Bug 1858145

Summary:	Host errata status not refresh after CV publish/promote
Product:	Red Hat Satellite	Reporter:	Hao Chang Yu <hyu>
Component:	Errata Management	Assignee:	Jeremy Lenz <jlenz>
Status:	CLOSED ERRATA	QA Contact:	Tasos Papaioannou <tpapaioa>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.7.0	CC:	ahumbe, jjeffers, jturel
Target Milestone:	6.9.0	Keywords:	PrioBumpGSS, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1919436 (view as bug list)		Environment:
Last Closed:	2021-04-21 13:17:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Hao Chang Yu 2020-07-17 02:47:44 UTC

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

Comment 5 Bryan Kearney 2020-08-11 20:03:45 UTC

Upstream bug assigned to jlenz

Comment 6 Bryan Kearney 2020-09-16 20:03:56 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30427 has been resolved.

Comment 7 Brad Buckingham 2021-01-08 21:02:03 UTC

The fix for this one is already in the early Satellite 6.9 snaps; therefore, aligning to release and updating state.

Comment 8 Tasos 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.

Comment 11 errata-xmlrpc 2021-04-21 13:17:39 UTC

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