Bug #20824
closed
Updating Oscap content "Red Hat rhel6 default content" with organization or location lead to error page
Description
Description of problem:
Oops, we're sorry but something went wrong ERROR: duplicate key value violates unique constraint "index_scaptimony_scap_content_profiles_scipi" DETAIL: Key (scap_content_id, profile_id)=(3, xccdf_org.ssgproject.content_profile_stig-rhel6-workstation-upstream) already exists.
How reproducible:
Always
Steps to Reproduce:
1. create an organization test_org
2. select any context organization
3. goto Hosts => SCAP contents
4. press edit button for "Red Hat rhel6 default content"
5. Goto Organization tab
6. select test_org
7. press submit
Actual results:
an error page is displayed with message
"Oops, we're sorry but something went wrong ERROR: duplicate key value violates unique constraint "index_scaptimony_scap_content_profiles_scipi" DETAIL: Key (scap_content_id, profile_id)=(3, xccdf_org.ssgproject.content_profile_stig-rhel6-workstation-upstream) already exists."
Expected results:
OSCAP content should successfully updated
Additional info:
The Error page is displayed when we update the location
Note: There is no error updating "Red Hat rhel7 default content" or any other SCAP content
Updated by The Foreman Bot over 7 years ago
- Status changed from New to Ready For Testing
- Assignee set to Ondřej Pražák
- Pull request https://github.com/theforeman/smart_proxy_openscap/pull/55 added
Updated by Marek Hulán over 7 years ago
- Subject changed from Updating Oscap content "Red Hat rhel6 default content" with organization or location lead to error page to Updating Oscap content "Red Hat rhel6 default content" with organization or location lead to error page
- Translation missing: en.field_release set to 294
Updated by Ondřej Pražák over 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset smart_proxy_openscap|a279f3eb70cd97564fcc0ca8148d679e6e786dd6.