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
Upstream bug assigned to jlenz
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30427 has been resolved.
The fix for this one is already in the early Satellite 6.9 snaps; therefore, aligning to release and updating state.
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