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.
Description of problem:
When selecting a specific errata and view what hosts it's applicable to, it shows a list. When checking "Only show content hosts where the errata is currently installable in the host's Lifecycle Environment", it shows much larger list, almost all hosts. This isn't right
Installable always means applicable also. Applicable might not be installable (if not published). Errata can't be installable if it's not applicable.
So, errata which is installable for host is also applicable for host. So, applicable list should be larger than installable
Version-Release number of selected component (if applicable):
6.2
How reproducible:
Always
Steps to Reproduce:
1. Go to Content > Errata
2. Select one or more errata
3. Click apply
4. A list of host will be listed
5. Click on the checkbox "Only show content hosts where the errata is currently installable in the host's Lifecycle Environment"
6. New list will be populated with more hosts
Actual results:
I can see some host, which have installable errata but those hosts do not show up for applicable.
Expected results:
The list of the applicable host should be greater than the list of installable host, because Installable always means applicable also.
The following scenario allowed for recreation of the issue (prior to the fix):
Scenario (from UI)
- have multiple content hosts that have installable errata; however, have different errata for some of the hosts... e.g. host 1 has errata A & B, host 2 has errata A & B, host 3 has errata C
- go to Content > Errata
select errata id for A
- click 'Content Hosts'
- observe that hosts 1 & 2 are listed
- click checkbox next to 'Only show content hosts where the errata is currently installable in the host's Lifecycle Environment.'
Result:
- all 3 hosts are shown; however, host 3 does not need errata A
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/RHBA-2017:1191