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:
Bug 1699786 fixed the host errata count after publishing/promoting a CV but the hosts' errata status are not recalculated.
Steps to Reproduce:
1. Go to Web UI -> Administer -> Settings -> Content -> Installable errata from Content View -> Yes
2. To simulate a host has updated errata, you can make use of CV filtering to exclude all the ET from the CV
3. Register a host to the CV and enable repos.
4. Ensure the host has green status flag. Hosts -> hostname page -> Errata status shows "All errata applied"
5. Remove the exclude filter from the CV and then publish a new version.
6. Revisit the host page.
Actual results:
Errata status still showing "All Errata applied" even the host has some installable errata
Expected results:
Update Errata status
The fix for this one is already in the early Satellite 6.9 snaps; therefore, aligning to release and updating state.
Comment 8Tasos Papaioannou
2021-02-03 15:56:57 UTC
Verified on 6.9.0 snap 11.0.
1.) Navigate to Administer > Settings > Content. Change 'Installable errata from Content View' to Yes.
2.) Import a manifest. Enable and sync the Red Hat Software Collections RPMs for Red Hat Enterprise Linux 7 Server x86_64 7Server repo.
3.) Create, publish, and promote a content view, with a filter that excludes RHBA-2020:5282.
4.) Create an activation key for the new content view and lifecycle environment, and register the content host.
5.) Install rh-ruby25-ruby available from the content view:
# yum -y install rh-ruby25-ruby
# rpm -q rh-ruby25-ruby
rh-ruby25-ruby-2.5.5-7.el7.x86_64
6.) Verify in the web UI that the content host has a green status flag. The content host's Details tab shows no installable errata.
7.) Remove the exclude filter from the content view, then publish and promote a new version.
8.) Verify that the content host now shows 1 bug fix erratum applicable/installable.
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 (Moderate: Satellite 6.9 Release), 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-2021:1313