Bug 2071413 - swtpm Fails to Upgrade After system-upgrade F36
Summary: swtpm Fails to Upgrade After system-upgrade F36
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: swtpm
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stefan Berger
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-03 17:36 UTC by Garry T. Williams
Modified: 2022-05-09 19:21 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-05-09 19:21:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Garry T. Williams 2022-04-03 17:36:55 UTC
Description of problem:
dnf fails with:

  Upgrading        : swtpm-0.7.2-1.20220307git21c90c1.fc36.x86_64       159/315
error: lsetfilecon: (/usr/bin/swtpm;6249a295, system_u:object_r:swtpm_exec_t:s0) Invalid argument
error: Plugin selinux: hook fsm_file_prepare failed

Error unpacking rpm package swtpm-0.7.2-1.20220307git21c90c1.fc36.x86_64
  Cleanup          : libvirt-8.0.0-3.fc36.x86_64                        160/315
error: unpacking of archive failed on file /usr/bin/swtpm;6249a295: cpio: (error 0x2)
error: swtpm-0.7.2-1.20220307git21c90c1.fc36.x86_64: install failed

  Running scriptlet: libvirt-daemon-driver-storage-8.0.0-3.fc36.x86_6   161/315
...
  Running scriptlet: libvirt-daemon-8.1.0-2.fc36.x86_64                 314/315
error: swtpm-0.7.2-1.20220307git21c90c1.fc35.x86_64: erase skipped

  Running scriptlet: libvirt-daemon-driver-storage-core-8.1.0-2.fc36.   314/315
...
Failed:
  swtpm-0.7.2-1.20220307git21c90c1.fc35.x86_64
  swtpm-0.7.2-1.20220307git21c90c1.fc36.x86_64

Error: Transaction failed

So, the f35 version remains.


Version-Release number of selected component (if applicable):
0.7.2-1.20220307git21c90c1.fc36


How reproducible:
Always


Steps to Reproduce:
1. Install swtpm in f35
2. Do dnf system-upgrade
3.

Actual results:
Error trying to upgrade swtpm to f36 release.


Expected results:
Successful upgrade

Comment 1 grumpey0 2022-04-03 18:32:01 UTC
Possibly a duplicate of Bugzilla report: #2056303

Comment 2 Zdenek Pytela 2022-04-13 15:01:34 UTC
Do you have any additional selinux modules installed?

  # semodule -lfull | grep -v ^100

Comment 3 Garry T. Williams 2022-04-13 22:08:39 UTC
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
$

Comment 4 Stefan Berger 2022-04-14 18:25:25 UTC
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.

Comment 5 Zdenek Pytela 2022-04-14 18:49:56 UTC
The problem is convoluted, currently I suppose swtmp is not a part of the problem though.

Comment 6 Zdenek Pytela 2022-04-20 17:16:34 UTC
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.

Comment 7 Stefan Berger 2022-05-09 12:51:29 UTC
I upgraded one of my systems last week and did not encounter this issue.


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