Description of problem: Red Hat errata shall be associated with Red Hat channels only. channel.software.clone allows that Version-Release number of selected component (if applicable): sat54 How reproducible: always Steps to Reproduce: 1. Clone a Red Hat channel, that contains Red hat errata using channel.software.clone API with False as the originalState parameter 2. check errata associated with the cloned channel Actual results: Red Hat errata associated with the cloned channel. That allows the user to act with the erratum like with a custom one (by most of the editing, he gets ISE) Expected results: Red Hat errata shall be cloned before associating with custom channels.
spacewalk.git: 41c17c45df6d61be16847cdebd5a337714bb5a48 drawback: this API call shall not get much slower by checking for available clones of the original errata or by the clone process, these operations are done async.
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. New Contents: Consequence: channel.software.clone allowed to associate Red Hat errata with custom channels. Result: When a Red Hat channel with associated Red Hat errata gets cloned using channel.software.clone API, Red Hat errata get cloned and only the cloned errata get associated with the cloned channel.
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. http://rhn.redhat.com/errata/RHBA-2011-1162.html