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 2150167 - Non-Applicable Errata displays as Installable Errata and triggers errors
Summary: Non-Applicable Errata displays as Installable Errata and triggers errors
Keywords:
Status: CLOSED DUPLICATE of bug 2178176
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Errata Management
Version: 6.11.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-02 00:23 UTC by Bianca House
Modified: 2023-05-08 14:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-08 14:25:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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