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 1869431 - Discrepancy between Satellite's applicable errata and Dnf's applicable errata
Summary: Discrepancy between Satellite's applicable errata and Dnf's applicable errata
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Errata Management
Version: 6.7.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: addubey
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-18 00:41 UTC by Hao Chang Yu
Modified: 2024-03-25 16:18 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-02 16:25:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 6961276 0 None None None 2022-05-31 09:11:32 UTC

Description Hao Chang Yu 2020-08-18 00:41:30 UTC 
Description of problem:
If an older module rpm is installed and there is a newer version of this normal rpm then a discrepancy will happen between Satellite and Dnf. Satellite considers the newer normal rpm as applicable because the older version of the module rpm is installed but Dnf doesn't allow newer normal rpm to be installed.

Steps to Reproduce:
From Satellite:
1. Create a epel 8 repo and sync it.

From Host:
1. Register a RHEL 8 host to the Default Org Library environment.
2. Enable baseos, appstream and the epel 8 repos
3. Install the "container-tools:rhel8" module

# yum module install container-tools:rhel8

4. "libslirp-4.3.1-1.el8" is not showing as available packages.

# dnf list libslirp
Installed Packages
libslirp.x86_64                          4.3.0-3.module+el8.2.1+6816+bedf4f91                          @rhel-8-for-x86_64-appstream-rpms

5. Just to make sure profile is up-to-date

dnf uploadprofile --force-upload

6. If you go to the Satellite Web UI -> Content Hosts -> the RHEL 8 host -> Errata page, you will found that "FEDORA-EPEL-2020-ff58160b15" erratum for "libslirp-4.3.1-1.el8" is still applicable.

Actual results:
Discrepancy between Satellite and Dnf

Expected results:
No Discrepancy
Comment 6 Hao Chang Yu 2020-09-30 09:38:11 UTC 
Ok. I can confirm that this is the Pulp bug. Dnf is working correct. The normal rpm shouldn't update the modular rpm of the installed and enabled module.

Pulp calculates the applicable rpms in each bound repository one by one. The normal 'libslirp' rpm is in the Epel repository, but the modular 'libslirp' rpm for the installed 'container-tools' module is in the appstream repository. Pulp should exclude all dependency rpms for the installed and enabled modules. When calculating the applicable rpms in the Epel repo, Pulp doesn't see the installed modules and their dependency rpms. Thus, the normal 'libslirp' rpm is incorrectly consider as applicable.

To fix this issue, the installed modules and their dependency rpms will need to be seen when calculating the applicable rpms for every bound repos.
Comment 10 Justin Sherrill 2021-01-27 15:24:47 UTC 
This will be resolved in 6.10 by the change to katello for applicability calculations
Comment 11 Ian Ballou 2022-08-02 16:25:29 UTC 
It's looking to me like this is fixed in Satellite 6.10+.  I'm going to close the issue since it's not feasible to fix on 6.9.  Feel free to reopen it if someone is able to reproduce the issue on 6.10+.
Note You need to log in before you can comment on or make changes to this bug.