+++ This bug was initially created as a clone of Bug #1065998 +++ Description of problem: Adding custom errata to clone of a custom channel creates cloned errata instead of source errata being just published into the target channel. Version-Release number of selected component (if applicable): spacewalk-java-2.1.152-1.el6.noarch How reproducible: always Steps to Reproduce: 1. Have a custom channel with few custom erratas in it 2. Clone that channel to new channel with no erratas 3. Note number of erratas shown in Errata -> Manage Errata 4. Add one of the errata to cloned channel using: Channel -> Manage Software Channels -> <your_cloned_channel> -> -> Errata -> Add -> Add Custom Errata 5. Select some errata and use confirmation button to add it 6. Note number of erratas shown in Errata -> Manage Errata Actual results: a) When you do point "5." above informational box appears saying "...scheduled 1 errata to be cloned to channel..." (note that "to be *cloned*" instead of "to be added") b) Numbers from points "3." and "6." do not match => new erratum was created c) When you locate original/source and cloned/target erratum in Errata -> -> Manage Errata they have only one channel selected in their "Channels" tab Expected results: a) Message should not mention cloning when I'm adding b) Counts should match c) I would expect that result would be that original/source erratum have 2 channel checked in the Channels tab Additional info: This docs have some info on erratum cloning (maybe I do not understand the concept enough, but IMO I do): https://access.redhat.com/site/documentation/en-US/Red_Hat_Satellite/5.6/html-single/Getting_Started_Guide/index.html#sect-Getting_Started_Guide-Channel_Management-Creating_and_Managing_Custom_Channels-Manage_Software_Channel_Details --- Additional comment from Jan Hutař on 2014-02-18 14:14:17 CET --- Checked on Satellite 5.4.1 and 5.5.0 and 5.6.0 and it behaves in the same way, so this is not a regression. I'm just unsure it is a correct behavior. --- Additional comment from Lukáš Hellebrandt on 2014-02-24 13:59:17 CET --- This doesn't only apply to cloned channels but to all custom channels
This one has been cloned already. Closing. *** This bug has been marked as a duplicate of bug 1141283 ***