Bug 643436

Summary: satellite-sync returns SQL error when retrieving product names data, but continues in sync
Product: Red Hat Satellite 5 Reporter: Pavel Novotny <pnovotny>
Component: UpgradesAssignee: Milan Zázrivec <mzazrivec>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: high Docs Contact:
Priority: high    
Version: 540CC: cperry
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-15 15:57:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 487677    
Attachments:
Description Flags
Log from sync process. none

Description Pavel Novotny 2010-10-15 15:40:57 UTC
Created attachment 453749 [details]
Log from sync process.

Description of problem:
After Satellite upgrade from 5.2.1 to 5.4 with external DB upgrade from oracle-10g to 11g, satellite-sync returnes SQL error when retrieving product names data. But the sync process does not crash after that and continues as usual.

Version-Release number of selected component (if applicable):
# rpm -q rhn-upgrade
rhn-upgrade-5.4.0.8-1.el5sat
# rhn-schema-version 
5.4.0.8-1.el5sat
# rpm -q spacewalk-schema
spacewalk-schema-1.2.21-7.el5sat

How reproducible:
Always

Steps to Reproduce:
1. run 'satellite-sync -c <your_channel>'
   (doesn't matter if you have fully synced the channel earlier or not)
2. Wait to the moment, when sync says "Retrieving / parsing product names data"
3. See the stacktrace with SQL error
  
Actual results:
Python stacktrace with SQL error:
(1, 'ORA-00001: unique constraint (PNOVOTNY.RHN_PRODUCTNAME_NAME_UQ) violated\n', "insert into rhnProductName (id, label, name) values (sequence_nextval('rhn_productname_id_seq'), :product_label, :product_name)")

Expected results:
No SQL error.

Additional info:
See full log from sync process in attachment.

Comment 1 Clifford Perry 2010-10-15 15:57:15 UTC

*** This bug has been marked as a duplicate of bug 636561 ***