Bug #9127
closedPGError: ERROR: duplicate key value violates unique constraint "index_scaptimony_xccdf_results_on_name"
Description
The upgrade to latest version of foreman was done a few weeks ago via puppet. All was fine at that time.
Today we updated the foreman puppet modules and the run tried to execute Foreman::Rake[db:seed]. This is what we got:
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: rake aborted!
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: PGError: ERROR: duplicate key value violates unique constraint "index_scaptimony_xccdf_results_on_name"
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: DETAIL: Key (name)=(pass) already exists.
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: : INSERT INTO "scaptimony_xccdf_results" ("name") VALUES ($1) RETURNING "id"
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns:
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Tasks: TOP => db:seed
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: (See full trace by running task with --trace)
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Seeding /usr/share/foreman/db/seeds.d/03-auth_sources.rb
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Seeding /usr/share/foreman/db/seeds.d/03-permissions.rb
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Seeding /usr/share/foreman/db/seeds.d/03-roles.rb
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Seeding /usr/share/foreman/db/seeds.d/04-admin.rb
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Seeding /usr/share/foreman/db/seeds.d/05-taxonomies.rb
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Seeding /usr/share/foreman/db/seeds.d/06-architectures.rb
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Seeding /usr/share/foreman/db/seeds.d/07-config_templates.rb
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Seeding /usr/share/foreman/db/seeds.d/08-partition_tables.rb
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Seeding /usr/share/foreman/db/seeds.d/10-installation_media.rb
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Seeding /usr/share/foreman/db/seeds.d/11-smart_proxy_features.rb
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Seeding /usr/share/foreman/db/seeds.d/13-compute_profiles.rb
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Seeding /usr/share/foreman/db/seeds.d/15-bookmarks.rb
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Seeding /usr/share/foreman/db/seeds.d/16-mail_notifications.rb
Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: All seed files executed
Error: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
Error: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
Updated by Dominic Cleal about 9 years ago
- Project changed from Foreman to Plugins
You may need to raise this with the OpenSCAP project over at https://github.com/OpenSCAP/scaptimony, I'm not sure they use Redmine. I'll CC someone who works on it.
Updated by cristian falcas about 9 years ago
I've opened an issue on the project page. Thank you.
Updated by Anonymous almost 7 years ago
- Status changed from Pending to Resolved
should be resolved by now