Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1141283

Summary: adding custom errata to a custom channel creates cloned errata
Product: Red Hat Satellite 5 Reporter: Tomas Lestach <tlestach>
Component: WebUIAssignee: Tomas Lestach <tlestach>
Status: CLOSED DEFERRED QA Contact: Dimitar Yordanov <dyordano>
Severity: medium Docs Contact:
Priority: medium    
Version: 560CC: dyordano, jhutar, lhellebr, satqe-list
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spacewalk-java-2.3.8-59 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1065998 Environment:
Last Closed: 2018-04-09 16:07:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1162131    

Description Tomas Lestach 2014-09-12 15:28:07 UTC
+++ 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

Comment 1 Tomas Lestach 2014-09-12 15:45:49 UTC
Moving to MODIFIED, since the bug was fixed within upstream Bug 1065998 with commit ...
spacewalk.git: fbfa7542885634d8302641dfa381664f4cdeb308

Comment 4 Tomas Lestach 2014-09-25 15:54:25 UTC
*** Bug 1146623 has been marked as a duplicate of this bug. ***

Comment 5 Tomas Lestach 2014-09-25 15:56:30 UTC
*** Bug 1141279 has been marked as a duplicate of this bug. ***

Comment 6 Tomas Lestach 2014-09-25 15:59:36 UTC
For QA - please, make sure you carefully test the custom errata cloning.
Several changes have been done in this area.
Especially - already associated errata won't be offered to be added to the channel again. (c159cbcd)

Comment 12 Tomas Lestach 2018-04-09 16:07:02 UTC
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. 

Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.