Hello there! I've never seen this error before `error: Plugin selinux: hook fsm_file_prepare failed` but I would try `dnf reinstall container-selinux` and maybe `dnf reinstall podman`

Hope this helps On Thu, Mar 31, 2022 at 4:27 AM Nathanael D. Noblet <nathanael(a)gnat.ca&gt; wrote: Hello,   Just wondering if this is a bug and what to report against. I upgraded from F35 to F36Beta last night. Today I ran `sudo dnf update` and saw some odd output. Not sure if its a bug with dnf or selinux or the packages being installed. Let me know if its a known issue or if I need to file a bug and where. Running transaction   Preparing        : 1/1   Upgrading        : crun-1.4.4-1.fc36.x86_64 1/16 error: lsetfilecon: (/usr/bin/crun;62451078, system_u:object_r:container_runtime_exec_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package crun-1.4.4-1.fc36.x86_64   Upgrading        : containers-common-4:1-53.fc36.noarch 2/16 error: unpacking of archive failed on file /usr/bin/crun;62451078: cpio: (error 0x2) error: crun-1.4.4-1.fc36.x86_64: install failed error: lsetfilecon: (/var/lib/containers/sigstore, system_u:object_r:container_var_lib_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package containers-common-4:1-53.fc36.noarch   Upgrading        : conmon-2:2.1.0-2.fc36.x86_64 3/16 error: unpacking of archive failed on file /var/lib/containers/sigstore: cpio: (error 0x2) error: containers-common-4:1-53.fc36.noarch: install failed error: lsetfilecon: (/usr/bin/conmon;62451078, system_u:object_r:conmon_exec_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package conmon-2:2.1.0-2.fc36.x86_64   Upgrading        : podman-3:4.0.2-1.fc36.x86_64 4/16 error: unpacking of archive failed on file /usr/bin/conmon;62451078: cpio: (error 0x2) error: conmon-2:2.1.0-2.fc36.x86_64: install failed error: lsetfilecon: (/usr/bin/podman;62451078, system_u:object_r:container_runtime_exec_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package podman-3:4.0.2-1.fc36.x86_64   Upgrading        : runc-2:1.1.1-1.fc36.x86_64 5/16 error: unpacking of archive failed on file /usr/bin/podman;62451078: cpio: (error 0x2) error: podman-3:4.0.2-1.fc36.x86_64: install failed error: lsetfilecon: (/usr/bin/runc;62451078, system_u:object_r:container_runtime_exec_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package runc-2:1.1.1-1.fc36.x86_64   Upgrading        : swtpm-0.7.2-1.20220307git21c90c1.fc36.x86_64 6/16 error: unpacking of archive failed on file /usr/bin/runc;62451078: cpio: (error 0x2) error: runc-2:1.1.1-1.fc36.x86_64: install failed error: lsetfilecon: (/usr/bin/swtpm;62451078, 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   Upgrading        : snapd-2.54.4-1.fc36.x86_64 7/16 error: unpacking of archive failed on file /usr/bin/swtpm;62451078: cpio: (error 0x2) error: swtpm-0.7.2-1.20220307git21c90c1.fc36.x86_64: install failed error: lsetfilecon: (/etc/sysconfig/snapd;62451078, system_u:object_r:snappy_config_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package snapd-2.54.4-1.fc36.x86_64   Running scriptlet: flatpak-1.12.7-1.fc36.x86_64 8/16 error: unpacking of archive failed on file /etc/sysconfig/snapd;62451078: cpio: (error 0x2) error: snapd-2.54.4-1.fc36.x86_64: install failed   Upgrading        : flatpak-1.12.7-1.fc36.x86_64 8/16 error: lsetfilecon: (/usr/libexec/flatpak-system-helper;62451078, system_u:object_r:flatpak_helper_exec_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package flatpak-1.12.7-1.fc36.x86_64 _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure -- and thanks for all the fish, Carmelo Sarta Red Hat<https://www.redhat.com/> csarta(a)redhat.com @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com/> _______________________________________________ devel mailing list --devel(a)lists.fedoraproject.org To unsubscribe send an email todevel-leave(a)lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/devel@lists.fedora... Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure

On 3/31/22 14:10, Daniel Walsh wrote: > On 3/31/22 02:35, Carmelo Sarta wrote: >> Hello there! >> I've never seen this error before >> `error: Plugin selinux: hook fsm_file_prepare failed` >> but I would try >> `dnf reinstall container-selinux` >> and maybe >> `dnf reinstall podman` > There seems to be an error appening when people are installing > container-selinux, that I have not pinned down.  It does not happen on > my system. There's a bug on this now as well: https://bugzilla.redhat.com/show_bug.cgi?id=2070942 Should I reassign to container-selinux?

Nathanael D. Noblet kirjoitti 31.3.2022 klo 5.26: > Hello, > >    Just wondering if this is a bug and what to report against. I > upgraded from F35 to F36Beta last night. Today I ran `sudo dnf update` > and saw some odd output. Not sure if its a bug with dnf or selinux or > the packages being installed. Let me know if its a known issue or if I > need to file a bug and where. There is a Bugzilla entry for this [1]. If you are like me and try to recover by doing selinux relabeling, you can end up in a situation where login is not possible anymore [2]. This seems to be affecting multiple users, so perhaps this is worth reporting as a Common Bug [3]. I will do so a bit later, unless somebody beats me to it.

On Thu, Mar 31, 2022 12:16:43 +0300, Otto Urpelainen wrote: > Otto Urpelainen kirjoitti 31.3.2022 klo 11.22: >> Nathanael D. Noblet kirjoitti 31.3.2022 klo 5.26: >>> Hello, >>> >>>    Just wondering if this is a bug and what to report against. I >>> upgraded from F35 to F36Beta last night. Today I ran `sudo dnf update` >>> and saw some odd output. Not sure if its a bug with dnf or selinux or >>> the packages being installed. Let me know if its a known issue or if I >>> need to file a bug and where. >> >> There is a Bugzilla entry for this [1]. >> If you are like me and try to recover by doing selinux relabeling, >> you can end up in a situation where login is not possible anymore [2]. >> >> This seems to be affecting multiple users, >> so perhaps this is worth reporting as a Common Bug [3]. >> I will do so a bit later, unless somebody beats me to it. > > Ok, I tried, but ask.fedoraproject.org gives me a permission error > when I click Create Topic. > (In Finnish, even though I changed the UI language to English > so that I could paste the error here.) > After running into multiple issues with discussion.fedoraproject.org, > I am weary of Discourse. That's odd. Can you please try in a clean private or incognito window where you're not using any browser extensions/add-ons that may be blocking various bits?