Repository navigation
[14.5-stable] zedmanager: drive purge state machine to completion in doUpdate - #6874
Closed
milan-zededa wants to merge 1 commit into
Closed
milan-zededa wants to merge 1 commit into
milan-zededa wants to merge 1 commit into
Conversation
This was referenced Oct 20, 2026
Fix app instance getting permanently stuck in HALTING state with PurgeInprogress=BringDown during a purge operation. The purge state machine has the following transitions: DownloadAndVerify → BringDown → RecreateVolumes → BringUp The BringDown → RecreateVolumes transition was only implemented in removeAIStatus(), which is called from updateAIStatusUUID() when it observes PurgeInprogress==BringDown. However, doUpdate() also drives the DownloadAndVerify → BringDown transition and calls doRemove() inline. When doRemove() completes synchronously (no domain or network to tear down), doUpdate() falls through with PurgeInprogress still set to BringDown. If no subsequent event triggers updateAIStatusUUID() (e.g. no DomainStatus, AppNetworkStatus, or VolumeRefStatus changes), removeAIStatus() is never called and the state machine stalls. This happens in practice when: 1. A purge counter mismatch is detected on reboot 2. handleCreateAppInstanceStatus calls doUpdate directly 3. The low-priority app boot path (checkLowPriorityApps) calls doUpdate 4. doRemove completes instantly because nothing is running 5. Nothing triggers another status re-evaluation After doRemove() completes, drive the state machine forward to RecreateVolumes and call purgeCmdDone() to persist the purge counter. This ensures the purge completes regardless of which code path invoked doUpdate(), and prevents the purge from being re-detected on subsequent reboots. Signed-off-by: Mikhail Malyshev <mike.malyshev@gmail.com> (cherry picked from commit d66fc44)
milan-zededa
force-pushed
the
14.5-backport-5618-purge-doupdate
branch
from
October 22, 2026 14:16
595e80e to
416e5bc
Compare
rene
approved these changes
Oct 25, 2026
Contributor
|
The Eden #6875 carries an identical patch of this commit plus the #5742 backport, and passes |
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Backport of #5618 to
14.5-stable.Clean cherry-pick with
-xfromd66fc446a1, no conflicts.The PR has no evetest test of its own. It is the first of the purge fixes that
TestPurgeNeverActivatedApp(#6875) andTestVMAppPurgeAfterPowerCycle(#6880) run on top of.PR dependencies
None.
How to test and validate this PR
Run the purge tests of the apps suite (added to
14.5-stableby #6873), together with the other purge backports (#6875, #6880):Changelog notes
Fixed an application instance getting stuck in HALTING during a purge when nothing had to be torn down.
Checklist
For backport PRs (remove it if it's not a backport):
And the last but not least:
check them.