Bug 643436 - satellite-sync returns SQL error when retrieving product names data, but continues in sync
Summary: satellite-sync returns SQL error when retrieving product names data, but cont...
Keywords:
Status: CLOSED DUPLICATE of bug 636561
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Upgrades
Version: 540
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Milan Zázrivec
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: sat540-triage
TreeView+ depends on / blocked
 
Reported: 2010-10-15 15:40 UTC by Pavel Novotny
Modified: 2010-10-15 15:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-15 15:57:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Log from sync process. (4.60 KB, text/plain)
2010-10-15 15:40 UTC, Pavel Novotny
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.