Let agents idle for updates required by creation cancellation
This commit is contained in:
@@ -426,3 +426,13 @@ Docker command must return or time out before cleanup can run. Cancellation
|
||||
does not require the original creation to acknowledge completion. The agent
|
||||
records a removal tombstone before cleanup so a delayed creation command cannot
|
||||
recreate the instance, and resumes interrupted cleanup under the same operation ID.
|
||||
|
||||
While cancellation requires a newer agent, the controller pauses all command
|
||||
delivery to that host, including background observations and command replays.
|
||||
Older agents hold their update lock across a whole command batch; continuing to
|
||||
feed them work could otherwise starve the updater. Already delivered work can
|
||||
finish and report normally, and heartbeats continue. The next automatic update
|
||||
check can install the release once the batch has drained. When a heartbeat
|
||||
advertises cancellation support, delivery resumes with cancellation cleanup
|
||||
first. This controller-side hold also recovers cancellations already waiting
|
||||
on older agents. Hosts without automatic updates need the current installer.
|
||||
|
||||
Reference in New Issue
Block a user