Bug 2150167

Summary: Non-Applicable Errata displays as Installable Errata and triggers errors
Product: Red Hat Satellite Reporter: Bianca House <bihouse>
Component: Errata ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.11.3CC: akapse, pmoravec, raymond.rocker
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-08 14:25:15 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 Bianca House 2022-12-02 00:23:18 UTC
Description of problem: 

The errata shows for disabled modules. In other words, dnf update -y says nothing to do, but errata still show as being applicable in Satellite. These errata are for modules that are not enabled. So Satellite is showing errata for non-applicable errata and giving those hosts an error status.

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


How reproducible:

Settings -> Content -> Installable errata from Content View setting (both yes and no) and no change.

For example, the ruby 2.5 module is the default and enabled, errata is seen for ruby 2.6, 2.7, and 3.0, which are available modules but not enabled. 


Steps to Reproduce:
1. Enable modules
2. Disable available modules that are not needed

Actual results:

Errata for modules not enabled shows and triggers errors for hosts.

Expected results:

Errata for modules not enabled do not show.

Additional info:

Comment 1 Pavel Moravec 2022-12-22 16:03:59 UTC
Hello,
while I understand the logic behind the bug, I am unable to reproduce it. Could you please provide particular reproducer steps?

As e.g. what I did:
- have RHEL8 BaseOS+AppStream synced to Satellite
- registered RHEL8 client, fully updated, with all modularity disabled (default)
- enabled ruby:2.5 module
- installed the module
- check Errata applicability for the Host -> nothing

Same for container-tools module /o\.

Same on Sat6.11.4 and 6.12 (dont have 6.11.3 at hand but dont expect it behaves differently).

What are the reproducer steps, then?

Or can you share a reproducer Sat+Host?

Comment 2 Bianca House 2023-03-06 15:14:16 UTC
Hello Pavel,

Apologies for the delayed response to your inquiry.

I will see if I can provide a more particular way to reproduce the issue.

The customer did specify that it was occurring on a Disconnected Satellite 6.11.3 with RHEL 8.6 hosts.

Comment 3 Ray Rocker 2023-03-09 14:36:11 UTC
I have this problem also, only on our disconnected satellite. We are on Satellite 6.10.7.1.

The Red Hat content is provided to the disconnected satellite through repository-level export/import from our connected satellite.

Comment 4 Bianca House 2023-05-08 14:25:15 UTC
Hello Pavel,

I spoke with Joniel and he let me know that there is a duplicate bug, which has a fix in progress. The duplicate bug is 2178176

The exact issue was able to be reproduced on a disconnected Satellite.

*** This bug has been marked as a duplicate of bug 2178176 ***