Bug 1804234
| Summary: | yum false positive advisory if module enabled | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Jan Jansky <jjansky> | |
| Component: | yum | Assignee: | Jaroslav Mracek <jmracek> | |
| Status: | CLOSED ERRATA | QA Contact: | Jan Blazek <jblazek> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | high | |||
| Version: | 8.1 | CC: | amkulkar, bvassova, dstreit, fblinuxos, gary.ballantine, james.antill, jcastran, ktordeur, kupadhya, kwalker, lberton, lilhuang, mdomonko, mmraka, mwhitake, myoder, pdwyer, phess, pkratoch, plawate, ppisar, psegedy, sumit.srivastava, tlestach | |
| Target Milestone: | rc | Keywords: | Triaged | |
| Target Release: | 8.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | libdnf-0.63.0-1.el8 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1873006 (view as bug list) | Environment: | ||
| Last Closed: | 2021-11-09 19:52:16 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: | ||||
| Bug Depends On: | 1951409 | |||
| Bug Blocks: | 1654708, 1825061, 1873006 | |||
|
Description
Jan Jansky
2020-02-18 14:03:37 UTC
The problem is triggered by unique structure of RHBA-2019:3337 advisory.In past all advisories have a single section <pkglist> with only one <collection> inside. With modules in section <collection> information about modules <module> appeared to specify if advissory is applicable. But from 77 modular advisories 3 advisories have a different structure. They have multiple <collection> (RHBA-2019:3337 with 15 collections, RHBA-2020:0347 with 2 collections, RHBA-2019:3416 with 2 collections) in <pkglist> and each collection have different modules there. It means that we are not talking about applicability of advisory but about applicability of collection and only packages described in that collection. The present structure in libsolv puts all packages from advisory into a single list and all modules described in advisory also in list. Then there is no relation between modules and collection and package and collection. There are only two ways how to resolve the issue and both are very painful. Make new structure inside libsolv => incompatible change or change generation of advisory. Additionally - even after resolvement of this issue false positive detection of advisory will be still present in multicontext modules due data redundancy in advisory. I created two simplified reproducers - https://github.com/j-mracek/module_repos/tree/master/advisories. *** Bug 1791843 has been marked as a duplicate of this bug. *** *** Bug 1870131 has been marked as a duplicate of this bug. *** *** Bug 1884169 has been marked as a duplicate of this bug. *** I created a patch https://github.com/rpm-software-management/libdnf/pull/1151 that will resolve the final part of the issue. To resolve the issue it requires libdolv-0.7.17 and https://github.com/rpm-software-management/libdnf/pull/1082, First part of tests: https://github.com/rpm-software-management/ci-dnf-stack/pull/909 The second part of CI tests: https://github.com/rpm-software-management/ci-dnf-stack/pull/968 *** Bug 1926342 has been marked as a duplicate of this bug. *** *** Bug 2004748 has been marked as a duplicate of this bug. *** 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 (Moderate: dnf security and bug fix update), 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-2021:4464 |