Bug 1984402
| Summary: | Support RPM demodularization | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Petr Pisar <ppisar> | |
| Component: | libmodulemd | Assignee: | Petr Pisar <ppisar> | |
| Status: | CLOSED ERRATA | QA Contact: | Jan Blazek <jblazek> | |
| Severity: | unspecified | Docs Contact: | Mariya Pershina <mpershin> | |
| Priority: | high | |||
| Version: | 8.5 | CC: | cchouhan, jberan, jnovy, vhutsky | |
| Target Milestone: | beta | Keywords: | AutoVerified, Rebase, Triaged | |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | libmodulemd-2.13.0-1.el8 | Doc Type: | Enhancement | |
| Doc Text: |
.`libmodulemd` rebased to version 2.13.0
The `libmodulemd` packages have been rebased to version 2.13.0, which provides the following notable changes over the previous version:
* Added support for delisting demodularized packages from a module.
* Added support for validating `modulemd-packager-v3` documents with a new `--type` option of the `modulemd-validator` tool.
* Fortified parsing integers.
* Fixed various `modulemd-validator` issues.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1984403 (view as bug list) | Environment: | ||
| Last Closed: | 2021-11-09 19:40:51 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: | 1984403 | |||
| Bug Blocks: | 1805260 | |||
|
Description
Petr Pisar
2021-07-21 11:28:12 UTC
2.13.0 fixed a bug in parsing buildorder value. This version now complains on loading RHEL-8 repository:
# dnf module list --repoid pulp-appstream
Last metadata expiration check: 3:59:10 ago on Wed 21 Jul 2021 12:38:00 PM CEST.
Module yaml error: Failed to parse buildorder in component: 18446744073709551615: The integer value is larger than 9223372036854775807 [line 118 col 9]
Module yaml error: Failed to parse buildorder in component: 18446744073709551615: The integer value is larger than 9223372036854775807 [line 118 col 9]
Module yaml error: Failed to parse buildorder in component: 18446744073709551615: The integer value is larger than 9223372036854775807 [line 107 col 9]
Module yaml error: Failed to parse buildorder in component: 18446744073709551615: The integer value is larger than 9223372036854775807 [line 114 col 9]
Module yaml error: Failed to parse buildorder in component: 18446744073709551615: The integer value is larger than 9223372036854775807 [line 118 col 9]
Module yaml error: Failed to parse buildorder in component: 18446744073709551615: The integer value is larger than 9223372036854775807 [line 118 col 9]
Module yaml error: Failed to parse buildorder in component: 18446744073709551615: The integer value is larger than 9223372036854775807 [line 107 col 9]
Module yaml error: Failed to parse buildorder in component: 18446744073709551615: The integer value is larger than 9223372036854775807 [line 114 col 9]
AppStream from Pulp
Name Stream Profiles Summary
389-ds 1.4 389 Directory Server (base)
[...]
This is because these 4 builds:
container-tools:rhel8:8020120200601155013:ffd2803a:x86_64
container-tools:rhel8:8030020200923153805:2a301c24:x86_64
container-tools:rhel8:8030020201124131330:830d479e:x86_64
container-tools:rhel8:8030120210208205200:c127ee91:x86_64
contain an invalid value there. The affected buildorder looks like this:
libslirp:
rationale: Primary component of this module
ref: stream-container-tools-rhel8-rhel-8.3.0
buildorder: 18446744073709551615
arches: [aarch64, i686, ppc64le, s390x, x86_64]
Sources shows there was -1 value. A build system (MBS, libmodulemd?) misparsed the value and stored a bad one. This propagated to mirrors.
A good point is that we already have newer builds, e.g. container-tools:rhel8:8040020210407081426:59631bd5:x86_64, which correctly read -1.
So it effectively does not affect users. Those are historical builds superseded by newer ones.
A bad point is that the warning will annoy the users.
I will look if we can hide the warning by DNF. Or selectively ignore the error. If we cannot, I will revert the parser fix for
RHEL 8 to preserve the invalid, but silent behavior.
I resolved the DNF warnings by relaxing the parser. No warnings anymore, the old broken module builds can be processed again. I updated the merge request to apply a patch with the relaxation. A package version in RHEL 8 should not be higher than in RHEL 9. Therefore this upgrade can be pushed into RHEL 8 only after pushing to RHEL 9 (bug #1984403) which has not yet happened. Fixed in: commit 93951985e28c28d784bbb8b084bae6e428148e35 (HEAD -> rhel-8.5.0, ppisar/rhel-8.5.0-bug1984402, origin/rhel-8.5.0) Author: Petr Písař <ppisar> Date: Wed Jul 21 15:39:19 2021 +0200 Resolves: #1984402 - 2.13.0 bump *** Bug 2008248 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 (libmodulemd bug fix and enhancement 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/RHEA-2021:4405 |