Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionsthirugn@redhat.com
2015-03-10 19:16:49 UTC
Description of problem:
Incremental update publishes/promotes to incorrect lifecycle environments of a composite content view
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150303.0
How reproducible:
Always
Steps to Reproduce:
1. Create a content view cv1 and publish v1.0 and promote to Library, QE. Register and subscribe a content host ch1 to cv1 -> QE
2. Create a composite content view ccv2, add cv1 to it. Publish v1.0 - promote to Library, QE. Register and subscribe a content host ch2 to ccv2 -> QE
3. Go to Content -> Errata -> Select an errata which is applicable to both content hosts ch1 and ch2
4. Click Apply Errata
5. Both ch1 and ch2 will show up
6. Just select ch1, click Next
7. Click the check box to immediately apply the errata to the content host. Click confirm.
Actual results:
1 - cv1 is published with v1.1 for QE (works as expected)
2 - ch1 received the errata (works as expected)
3 - cch2 is published with v1.1 for both Library, QE (not sure why cch2 is published to both Library, QE) (Not works as expected)
Expected results:
For the 3rd item above, I really dont know the expected result, this is a design question
Additional info:
Moving to POST since upstream bug http://projects.theforeman.org/issues/9799 has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|3817b397dcb2a50fbf3682e9c06c3ec0e6190f90.
Comment 7sthirugn@redhat.com
2015-03-24 20:26:13 UTC
Verified.
Satellite-6.1.0-RHEL-7-20150320.1
Verification steps:
1. Create a content view cv1 and publish v1.0 and promote to Library, QE. Register and subscribe a content host ch1 to cv1 -> QE
2. Create a composite content view ccv2, add cv1 to it. Publish v1.0 - promote to Library, QE. Register and subscribe a content host ch2 to ccv2 -> QE
3. Go to Content -> Errata -> Select an errata which is applicable to both content hosts ch1 and ch2
4. Click Apply Errata
5. Both ch1 and ch2 will show up
6. Just select ch1, click Next
7. Click the check box to immediately apply the errata to the content host. Click confirm.
Actual results:
1 - cv1 is published with v1.1 for QE (works as expected)
2 - ch1 received the errata (works as expected)
3 - ccv2 is not updated at all (works as expected)
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2015:1592