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.
Created attachment 1320702[details]
Table where errata should be
Description of problem:
Using the 'Errata Installation' action from the Host Collection details page does not present applicable errata even though hosts in the collection have errata which are indeed applicable.
Version-Release number of selected component (if applicable): 6.3.0 Snap 13
How reproducible: Always
Steps to Reproduce:
1. Register a client into a content view which has applicable errata which are also applicable to the host.
2. Create a host collection and add the host above to it
3. Navigate to the Details tab for the host collection in (2) and select 'Errata Installation'
Actual results:
The table returns 0 results.
Expected results: The table should contain errata which are applicable to the hosts in the collection.
Additional info:
I discovered this while attempting to verify https://bugzilla.redhat.com/show_bug.cgi?id=1443816
Hi Walden,
Can you take a look at this one?
I have confirmed that the behavior works correctly in the upstream, but not in Satellite 6.3 SNAP 14; therefore, I suspect that we are missing a commit either in katello or bastion.
From an initial look, when the user clicks on 'Errata Installation' from the host collections details pane, the POST api/v2/hosts/bulk/installable_errata is sent to the server without including any content host ids. I.e.
excluded: {ids: []}
included: {ids: []}
Which results in the following response from the server:
errorMessage: ["No hosts have been specified."]
FailedQA
Version Tested:
Satellite-6.3 Snap 19
steps:
1. Registered a content host and has applicable errata
2. Created host collection and added host to it
3. Navigated to host collection and click on errata installation
It shows "There are no Errata associated with this Content Host to display."(see attachment)
VERIFIED
Version Tested:
Satellite-6.3 Snap 20
steps:
1. Registered content host
2. Created host collection and added host to host collection
3. Clicked on errata installation
Found listed errata which are applicable to the hosts in the collection.(see attachment)
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-2018:0336