Red Hat Bugzilla – 1228292 – Incremental Update: Unable to filter my content hosts with environment if the selected errata contains atleast one installable errata
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-04 14:38:29 UTC
Description of problem:
Incremental Update: Unable to filter my content hosts with environment if the selected errata contains atleast one installable errata
Version-Release number of selected component (if applicable):
Sat 6.1 GA Snap 7
How reproducible:
Always
Steps to Reproduce:
1. Navigate to Content -> Errata
2. Select multiple erratas (make sure to include atleast one installable errata)
3. Apply Errata
4. Select the check box - Only show content hosts where is currently installable in the host's Lifecycle Environment.
Actual results:
I had 6 erratas - 5 applicable and 1 installable errata for my content host. So I expected not to see my content host when I checked the check box. I assumed the content host will not be shown when atleast one of the selected errata is an applicable errata.
Expected results:
Do not show content host when the check box is checked if atleast one of the errata is an applicable errata in the list
Additional info:
Moving to POST since upstream bug http://projects.theforeman.org/issues/10705 has been closed
-------------
Walden Raines
Applied in changeset commit:katello|881198cd4da2c491d9c7362dbeefd030dc6a370f.
*** Bug 1226381 has been marked as a duplicate of this bug. ***
Comment 8sthirugn@redhat.com
2015-06-16 13:53:16 UTC
Failed.
Test scenario:
1. Select two erratas - one applicable and one installable for a content host
2. Click Apply Errata
3. Now try to apply the check box to show content hosts where the errata is currently installable in the host's Lifecycle environment
4. The content host is still shown although one of the selected errata is not in content host's lifecycle environment.