Bug 1814095 - Applicable errata not showing up for module stream errata
Summary: Applicable errata not showing up for module stream errata
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.8.0
Assignee: Partha Aji
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-17 02:00 UTC by Partha Aji
Modified: 2020-10-27 13:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 13:00:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 29488 0 Normal Closed Applicable errata not showing up for module stream errata 2020-10-28 17:26:39 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:01:07 UTC

Description Partha Aji 2020-03-17 02:00:07 UTC
Applicable errata not showing up or computed correctly module stream errata.

* Create a content view that has rhel8 appstream
* Publish the content view
* Have a rhel8 host consume off it
* On the host run the following
"""
$ dnf -y module install nodejs:10
$ dnf -y install nodejs
$ dnf -y downgrade nodejs 
"""

Now back on the above CV
* Create an errata excludes filter and exclude RHSA-2020:0579
* Publish the content view
* Content -> Errata
* Search for 'errata_id = RHSA-2020:0579'

Expected:
RHSA-2020:0579 shows up as applicable since the applicability is calculated according to the library environment.

Actual:
RHSA-2020:0579 does not show up in the applicable errata list and lets you apply it on the host.

Comment 3 Justin Sherrill 2020-03-17 12:45:49 UTC
This needs to be worked on by katello, not pulp.  It does not appear to be a regression, but likely is easier to reproduce now that we have proper filtering of errata within modules (i.e. a more artifical reproduction)

I'm proposing for 6.7.z since its not a regression.

Comment 4 Partha Aji 2020-04-06 22:37:55 UTC
Connecting redmine issue https://projects.theforeman.org/issues/29488 from this bug

Comment 5 Bryan Kearney 2020-04-07 00:04:23 UTC
Upstream bug assigned to paji

Comment 6 Bryan Kearney 2020-05-20 16:04:31 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29488 has been resolved.

Comment 8 Lai 2020-08-21 14:46:13 UTC
Followed the steps above outline by Partha, but instead used RHSA-2020:2848 for filtering and searching, since RHSA-2020:0579 is outdated.

Expected result:
RHSA-2020:2848 shows up as applicable since the applicability is calculated according to the library environment.

Actual result:
RHSA-2020:2848 showed up as applicable since the applicability is calculated according to the library environment.

Verified on 6.8.0_010.

Comment 11 errata-xmlrpc 2020-10-27 13:00:52 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 (Important: Satellite 6.8 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-2020:4366


Note You need to log in before you can comment on or make changes to this bug.