Bug 2071413
Summary: | swtpm Fails to Upgrade After system-upgrade F36 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Garry T. Williams <gtwilliams> |
Component: | swtpm | Assignee: | Stefan Berger <stefanb> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 36 | CC: | davide, marcandre.lureau, stefanb, zpytela |
Target Milestone: | --- | ||
Target Release: | --- | ||
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-05-09 19:21:46 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
Garry T. Williams
2022-04-03 17:36:55 UTC
Possibly a duplicate of Bugzilla report: #2056303 Do you have any additional selinux modules installed? # semodule -lfull | grep -v ^100 Interesting: $ sudo semodule -lfull | grep -v ^100 [sudo] password for garry: 400 hplip pp 400 my-rpmdb-fix cil 300 my-gdb pp 300 my-wall pp 200 cockpit pp 200 fail2ban pp 200 flatpak pp 200 mysql pp 200 smartmon pp 200 swtpm pp 200 swtpm_svirt pp $ swtpm was built from the same sources for Fedora 35 and 36. I doubt that swtpm can resolve the issue. My guess it's a dependency that introduces the problem. The problem is convoluted, currently I suppose swtmp is not a part of the problem though. After updating F35 packages from updates-testing repo, upgrade to F36 works for me now, please check that as well: sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-c5bee6b70f and then upgrade to F36. swtpm maintainers: I think this bz can be closed, but please wait until the updates get to F35 stable repo and are community tested. I upgraded one of my systems last week and did not encounter this issue. |