When rhnpush'ing a package that already existed, you used to be able to use --force to overwrite what was already there (in the channel). Now you cannot. When you try this, you get an error:
ORA-00001: unique constraint (RHNSAT.RHN_CNP_CID_NID_UQ) violated
ORA-06512: at "RHNSAT.RHN_CHANNEL", line 1091
ORA-06512: at line 1
Error Class Code: 23
Error Class Info: Could not update database entry.
and the 2nd package shows up under 'Manage software packages'. essentially it's been pushed to the satellite (again), but couldn't be associated to the channel because the package already existed.
so i had forgotten about the enable_nvrea config option. This only happens if enable_nvrea is enabled, which it is not by default in satellite (at least it shouldn't be).
SO this may not be such a high priority bug.
Lol - oh yeah - Forgot we have a config option to disable --force. This is known.
Still a bug, just not a satellite blocker :}
moving to -canfix
*** Bug 654886 has been marked as a duplicate of this bug. ***
Fixed in spacewalk.git commit d1a9e12d8b5409ab54c029a6a9b7e9f72d157a89
cherrypicked as commit 77ce12aab7b3f9b45a1386d66b38f0e3a0000045
err that cherrypick is commit 77ce12aab7b3f9b45a1386d66b38f0e3a0000045
Changing to VERIFIED:
Automated test (v1.0-1)
Please be so kind and add a few key words to the technical note of this
bugzilla entry using the following structure:
For details, see:
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
There is already nice text in errata.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.