You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Supported recovery after an interrupted start request on macOS — Multipass 1.16.3
#5488
We’re preparing a small, non-production test using Multipass client and daemon 1.16.3+mac on Apple Silicon macOS. Before running it, we want to establish the supported operator recovery procedure.
Suppose a multipass start <instance> request has reached the daemon, but the client times out, disconnects or is terminated before receiving the final result. We would treat the outcome as unknown and would not retry the start.
What supported procedure establishes that:
The original start request has finished or been cancelled and cannot subsequently start the instance.
The intended instance is stopped.
It remains stopped until a new explicit start request, assuming no other operator or client issues lifecycle commands.
Specifically, is multipass stop --force <instance> followed by multipass info <instance> reporting Stopped sufficient? Could an earlier queued or in-progress start take effect after that stop or status observation?
If that sequence is insufficient, please identify the supported recovery steps and evidence an operator should check. Please distinguish confirmation of completed recovery from command acceptance or a momentary stopped-state observation.
If this cannot be established on 1.16.3, please say so and identify whether a supported release provides a documented procedure. We are not requesting guaranteed shutdown during host or daemon failure.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hello Multipass maintainers,
We’re preparing a small, non-production test using Multipass client and daemon 1.16.3+mac on Apple Silicon macOS. Before running it, we want to establish the supported operator recovery procedure.
Suppose a
multipass start <instance>request has reached the daemon, but the client times out, disconnects or is terminated before receiving the final result. We would treat the outcome as unknown and would not retry the start.What supported procedure establishes that:
Specifically, is
multipass stop --force <instance>followed bymultipass info <instance>reportingStoppedsufficient? Could an earlier queued or in-progress start take effect after that stop or status observation?If that sequence is insufficient, please identify the supported recovery steps and evidence an operator should check. Please distinguish confirmation of completed recovery from command acceptance or a momentary stopped-state observation.
If this cannot be established on 1.16.3, please say so and identify whether a supported release provides a documented procedure. We are not requesting guaranteed shutdown during host or daemon failure.
Thank you,
Trudy Beicht
All reactions