Bug 1699786

Summary:	Installable Errata not recalculated after CV publish/promote
Product:	Red Hat Satellite	Reporter:	Pavel Moravec <pmoravec>
Component:	Content Views	Assignee:	Pavel Moravec <pmoravec>
Status:	CLOSED ERRATA	QA Contact:	Lai <ltran>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4.2	CC:	akarimi, bbuckingham, bwallace, huali, naijain, patalber, rcavalca, wclark, will_darton, zhunting
Target Milestone:	6.6.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sat-prio-proposed
Fixed In Version:	tfm-rubygem-katello-3.12.0.rc2-11	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-22 19:49:40 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 Pavel Moravec 2019-04-15 08:35:20 UTC

Description of problem:
Having a Content Host in a CV, promoting the CV to get a new errata installable to that C.Host, WebUI does not show the newly installable errata.


Version-Release number of selected component (if applicable):
Satellite 6.4.2


How reproducible:
100%


Steps to Reproduce:
1. Have a Content Host that lacks some errata (i.e. fully update it, and then run:

yum downgrade openssh openssh-clients openssh-server polkit bind-license bind bind-libs-lite -y

three times, to ensure few errata can be applied)

2. Have the C.Host in a Content View "frozen" in past (with exclude filter "errata newer than 1.1.2018")

3. Ensure the host has no applicable errata (due to the old content in the CV):
a) WebUI: Hosts -> Content Hosts -> "Installable Updates" for the C.H. shows nothing
b) Details of the Content Host shows in "Installable Errata" also nothing
c) In Errata tab of the C.Host, no errata installable either
d) yum update / yum --security check-update shows nothing

4. remove the exclude filter from the CV and publish the CV

5. wait till the CV publish is completed

6. re-check 3.


Actual results:
6.
a) and b) checks from 3) shows no applicable errata
c) and d) does show applicable errata


Expected results:
also a) and b) to show applicable errata


Additional info:
workaround: run:

foreman-rake katello:import_applicability

Comment 3 Pavel Moravec 2019-04-16 08:28:03 UTC

Yet another adjacent bug:

Changing CV of a C.Host, errata applicability is not recalculated at all. And here even import_applicability does not help, or reg.app. task doesnt help..:-o

(shall I file new BZ for that?)

Comment 4 Pavel Moravec 2019-04-16 13:20:59 UTC

(In reply to Pavel Moravec from comment #3)
> Yet another adjacent bug:
> 
> Changing CV of a C.Host, errata applicability is not recalculated at all.
> And here even import_applicability does not help, or reg.app. task doesnt
> help..:-o
> 
> (shall I file new BZ for that?)

Raised as https://bugzilla.redhat.com/show_bug.cgi?id=1700406

Comment 7 Bryan Kearney 2019-05-06 18:07:15 UTC

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

Comment 11 Lai 2019-06-19 19:37:09 UTC

Followed Pavel's step above with slight modification.

Steps to Reproduce:
1. Spin up a content host that is registered to the satellite.
2. Have a content view with some errata.
3. Fully update an errata and install a package (In this instance we did gzip).
4. Run yum downgrade gzip three times to ensure that it's 3 version down from the latest.
5. Create a yum filter on the content view which excludes the any errata that is newer than 1.1.2015 (This is based on the downgrade of the gzip from 2018 to 2015).  This will make the content host with the content view "frozen" in the past.
6. Ensure the host has no applicable errata (due to the old content in the CV):
a) WebUI: Hosts -> Content Hosts -> "Installable Updates" for the C.H. shows nothing
b) Details of the Content Host shows in "Installable Errata" also nothing
c) In Errata tab of the C.Host, no errata installable either
d) yum update / yum --security check-update shows nothing

7. remove the exclude filter from the CV and publish the CV
8. wait till the CV publish is completed
9. re-check 6.


Expected results:
a) b) c) and d) should show applicable errata

Actual results:
a) b) c) and d) does show applicable errata

Verified on 6.6 snap 7

Comment 13 Bryan Kearney 2019-10-22 19:49:40 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, 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-2019:3172