Bug #13085
closed
duplicate key value violates unique constraint errors
Description
This seems to be related to rails 4, errors that look like
PG::Error: ERROR: duplicate key value violates unique constraint "index_katello_repository_package_groups_on_pgid_repoid"
DETAIL: Key (package_group_id, repository_id)=(3, 2) already exists.
: INSERT INTO katello_repository_package_groups (package_group_id, repository_id, created_at, updated_at) VALUES (3, 2, '2016-01-08 14:28:11 UTC', '2016-01-08 14:28:11 UTC'), (4, 2, '2016-01-08 14:28:11 UTC', '2016-01-08 14:28:11 UTC')
409 Conflict
are popping up somewhat randomly.
One way to possibly recreate:
1. create repo, 2. sync repo, 3. create content view, 4. add repo to view, 5. publish view
also is seen during katello:reset
possibly race conditions?
Updated by John Mitsch almost 9 years ago
- Related to Tracker #9259: Rails 4 feature added
Updated by Brad Buckingham almost 9 years ago
Note: when i saw this error it was doing steps 1-5 after the katello:reset. The katello:reset itself did not report an error.
Updated by Eric Helms almost 9 years ago
- Translation missing: en.field_release set to 86
Updated by Eric Helms over 8 years ago
- Related to deleted (Tracker #9259: Rails 4 feature)
Updated by The Foreman Bot over 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/5902 added
Updated by Brad Buckingham over 8 years ago
- Assignee changed from Zach Huntington-Meath to John Mitsch
Updating owner based upon PR.
Updated by John Mitsch over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|c92c13fa113533fc8cf255e9d12038a4069067ec.