failed to finalize previous deployment

State: idle Warning: failed to finalize previous deployment error: Finalizing deployment: Finalizing SELinux policy: Child process exited with code 1 check journalctl -b -1 -u ostree-finalize-staged.service Deployments: ● ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable Digest: sha256:193f431d6b16926eeed85acf33c0e5b6434522805b11789394dc41b74f078636 Version: 40.20241020 (2024-10-21T05:04:01Z) LayeredPackages: code dotnet-sdk-8.0 snapd LocalPackages: lact-0.5.6-0.x86_64 proton-mail-1.1.0-1.x86_64 ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable Digest: sha256:023e98d12a3f68596c7d99a059a86977d873ac17c7bd105dc770d0cc598545c9 Version: 40.20241014 (2024-10-15T08:59:50Z) LayeredPackages: code dotnet-sdk-8.0 snapd LocalPackages: lact-0.5.6-0.x86_64 proton-mail-1.1.0-1.x86_64 I tired removing snapd but it doesn't seem to work it just resets to whatever my last working build was
8 Replies
doomhound
doomhoundOP2mo ago
setting enforcement to 0 didn't work, trying to remove snapd didn't work, tryign to reset rpm-ostree didn't work. I'm not sure what else to do I think i fixed it, had to rebase back to the current working version of 40.20241014 and that didn't work as soon as I reboot i get failed to finalize previous deployment setting selinux policy using kargs doesn't work as it still errors, i cant remove snapd and i cant turn off selinux enforcement policy im stuck in a loop
wolfyreload
wolfyreload2mo ago
Maybe try this to clear any pending deployments and temporary files
rpm-ostree cleanup -b -p
rpm-ostree cleanup -b -p
Then try your reset
rpm-ostree reset
rpm-ostree reset
ProjectNexus
ProjectNexus2mo ago
I am having the same issue as OP on an OLED Steam Deck with SELinux policy, minus the layered packages. I've attached a text file of my upgrade attempt in Terminal.
doomhound
doomhoundOP2mo ago
it seems to hang on a permissions issue access the snappy semodule doomhound@bazzite:~$ journalctl -b -1 -u ostree-finalize-staged.service Nov 01 10:21:09 bazzite systemd[1]: Finished ostree-finalize-staged.service - OSTree Finalize Staged Deployment. Nov 01 10:21:43 bazzite systemd[1]: Stopping ostree-finalize-staged.service - OSTree Finalize Staged Deployment... Nov 01 10:21:44 bazzite ostree[8328]: Finalizing staged deployment Nov 01 10:21:45 bazzite ostree[8328]: Copying /etc changes: 40 modified, 2 removed, 142 added Nov 01 10:21:45 bazzite ostree[8328]: Copying /etc changes: 40 modified, 2 removed, 142 added Nov 01 10:21:45 bazzite ostree[8328]: Refreshing SELinux policy Nov 01 10:21:45 bazzite ostree[8337]: libsemanage.semanage_direct_get_module_info: Unable to open snappy module lang ext file at /etc/selinux/targeted/tmp/modules/200/snappy/lang_ext. (No such file or directory). Nov 01 10:21:45 bazzite ostree[8337]: semodule: Failed! Nov 01 10:21:45 bazzite ostree[8328]: Refreshed SELinux policy in 228 ms Nov 01 10:21:45 bazzite ostree[8328]: error: Finalizing deployment: Finalizing SELinux policy: Child process exited with code 1 Nov 01 10:21:45 bazzite systemd[1]: ostree-finalize-staged.service: Control process exited, code=exited, status=1/FAILURE Nov 01 10:21:45 bazzite systemd[1]: ostree-finalize-staged.service: Failed with result 'exit-code'. Nov 01 10:21:45 bazzite systemd[1]: Stopped ostree-finalize-staged.service - OSTree Finalize Staged Deployment. doomhound@bazzite:~$ ls /etc/selinux/targeted/ active booleans.subs_dist contexts logins policy semanage.read.LOCK semanage.trans.LOCK setrans.conf seusers it looks like the tmp directory doesn't exist so it must be created during the upgrade process and is being given the incorrect file permissions or its not even being created @ProjectNexus the devs are blaming snap and not bothering to look further, you'll probably just have to re-install like I did they 100% made changes to selinux policy or inherited something from upstream RHEL
ProjectNexus
ProjectNexus2mo ago
That's the thing. I never used anything relating to Snap. Unfortunately I decided to just wipe and go back to official SteamOS ☹️
doomhound
doomhoundOP2mo ago
I might just go back to using arch as my daily
Want results from more Discord servers?
Add your server