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-06-19 16:43:10 UTC
Description of problem:
Incremental Update: Selected content hosts are not recognized after I used the checkbox to show only the content hosts where the errata is currently installable in the host's Lifecycle environment
Version-Release number of selected component (if applicable):
Sat 6.1 GA Snap 8 Compose 2
How reproducible:
Always
Steps to Reproduce:
1. Have two content hosts one which has access to the entire 7Server content and the other having erratum filters to filter out any errata after 1/1/2015
2. Navigate to Content -> Errata page
3. Select an errata which is applicable to one content host and installable to another content host
4. Click Apply Errata
5. Enable the check box "Only show content hosts where the errata is currently installable in the host's Lifecycle Environment." - This displays only one content host which is expected
6. Now select the displayed content host and click Next
Actual results:
I am taken to the page which showed "You must select at least one Content Host in order to apply Errata"
Expected results:
Errata should be applied to the selected content host
Additional info:
This scenario works if I didnt enable the checkbox in Step 5.
Moving to POST since upstream bug http://projects.theforeman.org/issues/10904 has been closed
-------------
Walden Raines
Applied in changeset commit:katello|b1f0448a1755e3526a201a3d81251d2458fb330c.