fix: prevent stuck power lock when restarting an offline server (k8s)#3
Merged
Merged
Conversation
Co-Authored-By: Bryce Anglin <brycemanglin@gmail.com>
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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.
Summary
Restarting (or stopping) an offline server on the Kubernetes environment left the panel stuck with
another power action is currently being processed for this server. The power lock was held for ~10 minutes per attempt, so every subsequent action returnedErrLockerLocked.Root cause: a stopped server's Pod still exists but in a non-running (
Succeeded/Failed) phase — a completed Pod is not auto-removed. On restart,HandlePowerActionacquires the power lock and callsWaitForStop:WaitForStop→Stop→ (signal-stop eggs) →Terminate(SIGTERM), which sees the Pod isn't running and returns without deleting it.WaitForStopthen callswaitForPodDeletion, which blocks for the fullduration(10 min) waiting for a deletion that never happens — holding the power lock the whole time.Fix: short-circuit
WaitForStopwhen the Pod is already gone or not running — the server is effectively stopped, so mark it offline and return immediately. A subsequentStartstill recreates the Pod viaOnBeforeStart, so no stale-Pod cleanup is lost.Also extracted the repeated
stopping → offlinetransition into amarkOffline()helper (reused inTerminate).Tests
Added
TestWaitForStopcovering restart-while-offline. The "Pod exists but not running" case blocks for the full timeout without the fix and returns immediately with it.go build ./...,go vet ./environment/kubernetes/..., andgo test ./...all pass.