Could be possibly related to this recently reported bug:
4 Likes
I had the same issue. I can confirm that this workaround works. I ran grub2-mkconfig and haven’t had the issue since.
Shame that some users have given up on Silverblue over it. 
1 Like
Have you done another deployment since the fix? For example can you layer a package? I tired the posted fix and it did work to let me boot into the new deployment that one time, but future deployments ran into the same problem.
2 Likes
i almost did… and I’m seriously thinking about it
I like the idea but the development of packages and developers don’t think on silverblue
happens with a repo file that uses repo_gpgcheck=1 (like tailscale), it turns google software unusable (a bug report exists). of course there’s a workaround (manually set repo_gpgcheck to 0), but then tailscale can’t be upgraded
now this
everytime that an update arrives … silverblue is an afterthought
Yes, I am able to layer new packages without the issue occurring.
2 Likes
Looks like it’s been reported upstream as an rpm-ostree issue. This means it also likely affects Kinoite, IoT, and Fedora CoreOS.
4 Likes
As a work-around, I used the rpm-ostree rollback command. After updating the system and running rpm-ostree status, the warning message is gone.
2 Likes
It sounds like you were able to revert back to before the bug was introduced. I’m curious if you now experience this bug on a future update attempt.
3 Likes
Having the same problem. Was able to fix it by using @fastoslinux’s workaround. Will see if it happens again with next update.
2 Likes
Can confirm, doing a rollback then upgrade again did the trick for me just now. No reported errors and no pending updates.
4 Likes
Are you able to do further deployments? For example can you layer a package and restart without doing anything out of the ordinary and have it work correctly?
3 Likes
Kionite. grub2-mkconfig Did the job as well. I thought I messed up laptop installation x)
4 Likes
I did an rpm-ostree update today, and everything worked fine – no need for sudo grub2-mkconfig. The new GRUB entry booted with no issue.
2 Likes
Another possible solution is sudo ostree admin finalize-staged as noted https://discussion.fedoraproject.org/t/update-again-and-again/41526
3 Likes
Well, I’m back 4 days later with the issue still happening. Every time I want to do a follow up sudo rpm-ostree upgrade I’m presented with the original problem and have to rollback, reboot, and then upgrade again. That seemingly takes, but then I try to perform the upgrade again, and I get the failed to finalize previous deployment.
I’ll try the sudo ostree admin finalize-staged after performing the upgrade.
1 Like
So, now I have tried to run these commands:
sudo rpm-ostree upgrade # I don't know if you NEED sudo
sudo ostree admin finalize-staged
sudo grub2-mkconfig
Rebooted, and everything seems to be going well. I read about these in this thread, and another here, then over at these two GitHub issues for rpm-ostree/3925 and fedora-silverblue/322. I also found a blog someone wrote which talks about how they fixed this as well, here. Whether or not these actually fix the issue is something I don’t know, but they make it so the updates successfully take.
I generally try to not layer on more packages than I need for Fedora Silverblue. Everything else is done through the Toolbox or Flatpaks.
2 Likes
Yes, but the idea is to test if layering a package works or not, regardless of if you regularly do it. If layering (and unlayering) a package does not work without workarounds then the core issue is not actually solved.
I tested this by layering in a package – I used hugo – and it worked as expected.
So for me, this issue appears to be resolved.
I didn’t need hugo layered (I run it both in a Toolbox and as a local binary), so I rolled back, which also worked.
4 Likes
I have the same problem with silverblue 36. I am trying to install the tkinter package using rpm-ostree, and when I run rpm-ostree status no extra packages are listed.
I have tried the various ‘fixes’, including grub2-mkconfig, and ostree admin finalize-staged, but no change. I can install tkinter into a toolbox, but not into my rpm-ostree install. I have tried installing a few gtk apps, but no luck.
rpm-ostree update seems to work.
I have tried a rollback and then an update, but I am still unable to install any packages successfully.