-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve ability to monitor running/canceled transactions #210
Comments
For starters, a different error message for cancellation cleanup would be helpful.
If we can make whatever the daemon is getting stuck on more responsive to cancellation then maybe we can sidestep the lack of status information in this state. |
Debugging a hang with
Stack trace after attaching to
|
This particular hang was fixed by ostreedev/ostree#181, but I think it's still worth addressing Micah's more general point with canceled transactions. |
I updated the title to be a bit more inclusive. I think it would be great if the client could get a status of the transaction(s) on the system. For example, user A starts
Or in the case of a canceled transaction like
And the case of no transactions:
Not sure if any or all of this data is available or the feasibility of generating such output, but it would improve some of the porcelain. |
I like that. The basic mechanics are already implemented: if you issue the exact same command from two different consoles (say, Don't think it would be too hard to let any client listen in on the messages. |
Fixed by #1019. |
With the introduction of daemon mode, it is possible to start a transaction like
rpm-ostree deploy
and then cancel out of the running transaction with the likes ofctrl-c
. This can leave the system in a state where future transactions run into the following error:error: System transaction in progress
Unfortunately, there is no way to observe the state of the transaction in progress and the user is forced to repeatedly try the future transaction until the daemon is ready again.
The text was updated successfully, but these errors were encountered: