I’m hoping someone can help me out with an issue I’m having with rpm-ostree. I tried to roll back to a previous deployment on my Kinoite system, but seem to have made things worse and now I’m not sure how to recover!
Here’s what happened:
I booted into an older deployment using the grub menu
Ran rpm-ostree rollback to try to make this the new default
Checked with rpm-ostree status but it seems to show the wrong/old version as default
Tried to deploy a specific commit hash with rpm-ostree deploy
Now status shows multiple commits with the same version and I’m not sure which is which
I’m afraid to reboot since I don’t know which version it will actually boot into. I think I must have misunderstood how rpm-ostree handles deployments and rollbacks.
Could someone please advise the best way to recover from this situation? I’m happy to provide any logs or additional details if it’s helpful to diagnose. I just want to get my system back to a good state before the next reboot.
Any guidance would be greatly appreciated! I’m still getting the hang of how rpm-ostree works under the hood. Thank you for your patience and for helping this beginner out!
Let me know if you need any other specifics to help me resolve this.
At some point my system froze due to nvidia driver issues (happens sometimes) and I had to restart. I attempted to boot into my last known good state again, which is the active boot you’ll see in the status.
I also found rpm-ostree cleanup which provides options to remove a rollback or pending change.
What I still can’t find is how to make the currently booted image the default. I tried getting its SHA and running rpm-ostree deploy <SHA>. It thought for awhile and then gave up. Is that the correct way to do this?
