Bug 1366629

Summary: Satellite upgrade fails with "duplicate key value violates unique constraint" error
Product: Red Hat Satellite Reporter: rakesh kumar <rakumar>
Component: Content ManagementAssignee: orabin
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: high Docs Contact:
Priority: high    
Version: 6.2.0CC: bbuckingham, jcallaha, mmccune, orabin, paji, xdmoon, zhunting
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
URL: http://projects.theforeman.org/issues/16137
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.0.0.73-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-22 06:36:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
content host details none

Comment 2 Bryan Kearney 2016-08-17 10:17:22 UTC
Upstream bug component is Content Management

Comment 3 Bryan Kearney 2016-08-18 02:17:18 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/16137 has been closed

Comment 6 jcallaha 2016-08-19 19:27:48 UTC
Verified in Satellite 6.2.1 Snap 1.3. Upgrade from Satellite 6.1.8 executed without issue.

registered content host to satellite with two activation keys and the installer handled it correctly.

[root@mgmt9 ~]# subscription-manager register --org="Default_Organization" --activationkey="sat61,sat62"
The system has been registered with ID: 12e157e3-383c-42f5-99f1-a3388d511c91 

Installed Product Current Status:
Product Name: Red Hat Enterprise Linux Server
Status:       Subscribed


See attached for content host details page.

Comment 7 jcallaha 2016-08-19 19:28:25 UTC
Created attachment 1192267 [details]
content host details

Comment 9 errata-xmlrpc 2016-08-22 06:36:27 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1643