❯ rpm-ostree cancel && rpm-ostree upgrade && flatpak update -y
Cancelling transaction: upgrade
Cancelled.
error: Transaction in progress: refresh-md
You can cancel the current transaction with `rpm-ostree cancel`
~
❯ rpm-ostree cancel && rpm-ostree upgrade && flatpak update -y
Cancelling transaction: refresh-md
Cancelled.
error: Transaction in progress: upgrade
You can cancel the current transaction with `rpm-ostree cancel`
~
❯ rpm-ostree cancel && rpm-ostree upgrade && flatpak update -y
Cancelling transaction: upgrade
Cancelled.
⠒ Scanning metadata: 1257...
Expected:
rpm-ostree often hangs at refresh-md, that’s why usually have to update manually – especially before a system restart. After stopping it via rpm-ostree cancel it’s still not possible to run it manually, as it seems to immediately restart its transaction. It should provide some time for executing it manually, say at least maybe 1-5 minutes before it restarts a transaction by itself.
Steps to reproduce it
I don’t know, if the refresh-md-blocking behaviour is wide-spread, so no idea.
Host system details
Expected vs actual behavior
Expected:
rpm-ostree
often hangs atrefresh-md
, that’s why usually have to update manually – especially before a system restart. After stopping it viarpm-ostree cancel
it’s still not possible to run it manually, as it seems to immediately restart its transaction. It should provide some time for executing it manually, say at least maybe 1-5 minutes before it restarts a transaction by itself.Steps to reproduce it
I don’t know, if the
refresh-md
-blocking behaviour is wide-spread, so no idea.