Description of problem: When cloning errata, newly generated cache contains the original erratum, not the clone. Version-Release number of selected component (if applicable): sat54 How reproducible: always Steps to Reproduce: 1. sync a rhel channel 2. create custom channel and set this custom channel as base of a your system 3. push some packages into the custom channel, for them there's an errata update (from the rhel channel) and make sure your system has the non-errata packages installed 4. Add Red Hat Erratum into your custom channel using the <custom_channel> - Errata - Add Red Hat Errata page that contains upgrades for the packages in the custom channel 5. Check <system> - Software - Errata page Actual results: Very baaad. In the errata list, that shall be applicable to your system you see the original Red Hat erratum (that isn't accessible for the system, because it's not pushed into the custom channel) I better do not try to apply the erratum to the system. Expected results: I'd like to see the clone erratum in the system applicable errata list.
spacewalk.git: 6e2282aa431e12e66e6d202956695550822568e8
Moving to Verified: Testing procedure: As per comment 0. Comparing the id of resulting errata. They are same with with spacewalk-java-1.2.39-80.el6sat.noarch They are distinct with spacewalk-java-1.2.39-82.el6sat.noarch Verified against: spacewalk-java-1.2.39-82
Verified in stage according to the procedure in initial comment w/ spacewalk-java-1.2.39-82 -> release pending.
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. https://rhn.redhat.com/errata/RHSA-2011-0879.html