Bug 2054921
| Summary: | dnf system-upgrade 35 to 36 fails with various pipewire wireplumber conflicts | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chris Murphy <bugzilla> |
| Component: | pipewire | Assignee: | Wim Taymans <wtaymans> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 36 | CC: | awilliam, bcotton, brunovern.a, bugzilla, gmarr, information, ldelouw, robatino, wtaymans |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | RejectedBlocker AcceptedFreezeException | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-25 19:11:42 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: | |||
| Bug Blocks: | 1953784 | ||
|
Description
Chris Murphy
2022-02-16 02:14:35 UTC
--allowerasing seems to work around this but I don't think we expect users to figure that out on upgrades do we? Proposed as a Blocker for 36-beta by Fedora user chrismurphy using the blocker tracking app because: For each one of the release-blocking package sets, it must be possible to successfully complete a direct upgrade from a fully updated, clean default installation of each of the last two stable Fedora releases with that package set installed. https://fedoraproject.org/wiki/Fedora_36_Beta_Release_Criteria#Upgrade_requirements I can't reproduce this in my test VM (although I do get a plocate conflict). I wouldn't think it matters, but if you disable the third-party repos, does that make a difference? No, this conflict remains, but then adds a bunch more (gstreamer, et al). What those messages are ultimately saying, I think, is that you currently have pipewire-media-session installed, but the upgrade wants to install wireplumber for some reason. Those two packages conflict, you're meant to have one or the other but not both. The key question here is "why does dnf specifically want to pull in wireplumber when pipewire-media-session is already installed?" The log messages don't answer that. If you still have the system in the pre-upgrade state, we may need to get more verbose info out of dnf somehow. I doubt this counts as a criteria validation because I don't think it would affect a clean F34 install (as pipewire-media-session didn't exist in F34 at all) or clean F35 install (F35 defaulted to wireplumber). I think it will only happen if you got pipewire-media-session along the way either by manually picking it, or by upgrading at some time where you wound up with it installed on upgrade (I think there were periods during F35 development where that happened). >The log messages don't answer that. If you still have the system in the pre-upgrade state, we may need to get more verbose info out of dnf somehow.
Yep. I have the pre-upgrade state in a btrf snapshot. The embarassing part is the dnf history proves this is not a Fedora 35 clean install.
Best I can tell, it's a clean install of Fedora 34, dnf system-upgrade to 35 on 30 Aug 2021, so after beta freeze, before beta GA. pipewire-media-session-0.3.33-3.fc35.x86_64 was installed during the system upgrade, and wireplumber doesn't appear in the transaction at all. The bug seems decently likely to be a testing artifact.
Yeah. There was a time during the F35 cycle where, on upgrade from F34, you'd get pipewire-media-session installed, but that wasn't the intention, and by Beta (IIRC) it was fixed so that on upgrade you got wireplumber. There probably is still a bug that could be resolved or mitigated here, but I think it's clearly not a blocker on current info. We might want to mention it in common bugs, though, as we know some people did manually switch to pipewire-media-session due to issues in wireplumber, and other people will be in your situation (got it during an early F35 cycle upgrade). The votes in https://pagure.io/fedora-qa/blocker-review/issue/612 are at -5, so rejecting this as a blocker. bcotton voted +1 FE, so marking as a proposed FE. Discussed during the 2022-02-28 blocker review meeting: [0] The decision to classify this bug as an "AcceptedFreezeException (Beta)" was made as it is a noticeable issue that cannot be fixed with an update. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-02-28/f36-blocker-review.2022-02-28-17.00.txt This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. |