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:
Host collections do not display errata information
Version-Release number of selected component (if applicable):
Tested on Sat 6.0.4 installed on RHEL 7
How reproducible:
Always
Steps to Reproduce:
1. Click on host collections
2. Click on a group
3. Click on actions
4. Click on Errata Installation
5. Click on a errata's ID
6. Look for the details of the errata, many fields are empty
Actual results:
Some empty fields
Expected results:
We should see all detailed information about the specific errata
Additional info:
Also, in the errata list, the column Affected Content Hosts is empty.
Comment 1RHEL Program Management
2014-10-30 13:23:04 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
I have tested this on a Satellite 6.1.1 GA install and am no longer observing
the behavior described.
RPMs installed:
ruby193-rubygem-katello-2.2.0.66-1.el7sat.noarch
foreman-1.7.2.34-1.el7sat.noarch
Attaching screenshot showing the errata details.
Tested with the procedure provided in the initial description on Satellite 6.2 Snap 5. The behavior is consistent with comment 4, in that detailed information pertaining to the erratum is provided to the user.
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-2016:1501