Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1822030 - libmodulemd fails to resolve current Fedora 30 repositories
Summary: libmodulemd fails to resolve current Fedora 30 repositories
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libmodulemd
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stephen Gallagher
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-08 06:18 UTC by Lars Karlitski
Modified: 2020-04-25 02:19 UTC (History)
3 users (show)

Fixed In Version: libmodulemd-2.9.3-1.fc31 libmodulemd-2.9.3-1.fc30 libmodulemd-2.9.3-1.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-16 22:40:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lars Karlitski 2020-04-08 06:18:24 UTC
Image Builder on Fedora 32 fails building Fedora 30 images, because libmodulemd seems to have become stricter about modules with the same ids but differing content.

When depsolving using Fedora 30 repositories, dnf fails with this error from libmodulemd:

    DNF error occured: RepoError: Error occurred when setting up repo: Failed to resolve: Encountered two streams with matching NSVCA testmodule:master:3020190304173846:a5b0195c:x86_64 but differing content

Fedora 30's repositories seem to contain a duplicate `testmodule`.

This is also reproducible with

    dnf --releasever=30 module list

(on Fedora 32).

It's probably correct to warn (or even fail) when encountering this error, but it is a backwards incompatible change. How does libmodulemd usually handle those, given that there are supported repositories still in use that are misconfigured like this? 

Thanks to Daniel Mach for helping to figure this out and coming up with the minimal reproducer.

Comment 1 Stephen Gallagher 2020-04-08 14:30:28 UTC
This was fixed in libmodulemd 2.9.2, which it appears I forgot to push to a bodhi update. I'll get that out immediately.

Comment 2 Lars Karlitski 2020-04-08 14:49:19 UTC
Thank you Stephen!

Comment 3 Fedora Update System 2020-04-08 16:10:00 UTC
FEDORA-2020-34b22b690d has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-34b22b690d

Comment 4 Fedora Update System 2020-04-08 16:10:01 UTC
FEDORA-2020-5f5da0cd13 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-5f5da0cd13

Comment 5 Fedora Update System 2020-04-08 16:10:02 UTC
FEDORA-2020-9268872640 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-9268872640

Comment 6 Fedora Update System 2020-04-09 18:38:17 UTC
FEDORA-2020-9268872640 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-9268872640`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-9268872640

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2020-04-09 19:13:45 UTC
FEDORA-2020-34b22b690d has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-34b22b690d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-34b22b690d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2020-04-09 20:14:20 UTC
FEDORA-2020-5f5da0cd13 has been pushed to the Fedora 30 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-5f5da0cd13`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-5f5da0cd13

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2020-04-16 22:40:51 UTC
FEDORA-2020-34b22b690d has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2020-04-18 02:31:35 UTC
FEDORA-2020-5f5da0cd13 has been pushed to the Fedora 30 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2020-04-25 02:19:27 UTC
FEDORA-2020-9268872640 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.