rpm-ostree troubles (InterruptedLiveCommit)
Hello, I was installing new packages on my Bazzite install using
rpm-ostree install --apply-live
(which did not have a Flatpak and cannot be installed onto a Distrobox without pulling the entirety of KDE). However, as it was finishing, this happened:
Indeed, upon checking the systemd journal, rpm-ostree
had an abort
and proceeded to coredump. Upon checking rpm-ostree status
, now it's like this:
I tried to do a rpm-ostree cleanup -p
in hopes this would revert me to the previous state, but that only removed the first image, leaving the current (interrupted) one and the one without layered packages, so now it's like this:
I also did an ostree fsck
, and this reported corrupted objects. However, I saw this was a known issue with container-based distros.
So, should I be worried, or could I just rpm-ostree rollback
and move on? I'd like to avoid removing all layered packages since rpm-ostree install
always takes ages to do anything.Solution:Jump to solution
TL;DR: A
rpm-ostree rollback
does seem to fix it. I'm going to wait and see whether the crash problem is transient or not.
EDIT: yep, transient problem. Fixed!...2 Replies
Oh, it seems doing
rpm-ostree rollback
does remove all of my packages. Fun!
Well, good time as any to consolidate all of my layered packages in one commit.Solution
TL;DR: A
rpm-ostree rollback
does seem to fix it. I'm going to wait and see whether the crash problem is transient or not.
EDIT: yep, transient problem. Fixed!