Bug 1869431
Summary: | Discrepancy between Satellite's applicable errata and Dnf's applicable errata | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Hao Chang Yu <hyu> |
Component: | Errata Management | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | addubey |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 6.7.0 | CC: | addubey, ahumbe, ajambhul, avnkumar, bshahu, iballou, jsherril, mkalyat, spurrier, ttereshc, vchepkov |
Target Milestone: | Unspecified | 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: | 2022-08-02 16:25:29 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
Hao Chang Yu
2020-08-18 00:41:30 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. This will be resolved in 6.10 by the change to katello for applicability calculations 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+. |