Bug 1814095

Summary:	Applicable errata not showing up for module stream errata
Product:	Red Hat Satellite	Reporter:	Partha Aji <paji>
Component:	Content Views	Assignee:	Partha Aji <paji>
Status:	CLOSED ERRATA	QA Contact:	Lai <ltran>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	jsherril
Target Milestone:	6.8.0	Keywords:	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:		Environment:
Last Closed:	2020-10-27 13:00:52 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 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