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.
Bug 1699786 - Installable Errata not recalculated after CV publish/promote
Summary: Installable Errata not recalculated after CV publish/promote
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.4.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.6.0
Assignee: Pavel Moravec
QA Contact: Lai
URL:
Whiteboard: sat-prio-proposed
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-15 08:35 UTC by Pavel Moravec
Modified: 2023-09-07 19:55 UTC (History)
10 users (show)

Fixed In Version: tfm-rubygem-katello-3.12.0.rc2-11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:49:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 26624 0 Normal Closed Installable Errata not recalculated after CV publish/promote 2020-12-23 14:47:25 UTC
Red Hat Knowledge Base (Solution) 4065781 0 Troubleshoot None [Satellite6] WebUI shows no installable errata for a Content Host despite new content from a CV publish/promote made som... 2019-04-16 07:18:53 UTC

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
Note You need to log in before you can comment on or make changes to this bug.