Description of problem: After pushing contents of fedora17/Packages to my custom channel I decided to repeat this process once more time, just to check if all packages have been successfully pushed. Error is shown at Additional info section Version-Release number of selected component (if applicable): Spacewalk 1.8 (Nightly) How reproducible: Seems as random bug for me, but I when I was repeating this process once more (to see if error message is gone) I still got error messages at exactly same point. Steps to Reproduce: 1. Upload some packages to custom channel. 2. Try to push these packages one more time. Actual results: Error message shown bellow. Error Message: ORA-00001: unique constraint (SPACEUSER.RHN_CNP_CID_NID_UQ) violated ORA-06512: at "SPACEUSER.RHN_CHANNEL", line 1096 ORA-06512: at line 1 Error Class Code: 23 Error Class Info: Could not update database entry. Expected results: No error
Reproducer: - have an rpm package - create a copy and sign it with different key - push both packages (the same NEVRA but different checksum) into a channel
Fixed in spacewalk master commit ad4647ef6281e83fa27d5ca0c4850a7365461f24 843374 - fixed subquery in FROM must have an alias commit 342fda667bf9eaa6c04458958954c49ab6abebd7 843374 - upgrade script for rhnChannelNewestPackageView commit a4505264511ff975fa64599ed04789300d47fdf2 fixed indentation commit e8cb44dfbf3d9f5cd6d673335cc932894d5cabf3 843374 - make list of newest packages unique there can be two packages with the same NEVRA but different checksum
Moving ON_QA. Packages that address this bugzilla should now be available in yum repos at http://yum.spacewalkproject.org/nightly/
Spacewalk 1.8 has been released: https://fedorahosted.org/spacewalk/wiki/ReleaseNotes18