Fix minikube role skipping start when kubelet/apiserver are stopped #137

Merged
eblume merged 1 commit from fix/minikube-status-check into main 2026-02-09 23:03:01 -08:00
Owner

Summary

  • After a power loss, minikube's Docker container (host) restarts but kubelet/apiserver remain stopped
  • The ansible role's status check used --format='{{.Host}}' which only examined the host VM state
  • When host=Running but kubelet/apiserver=Stopped, the role skipped minikube start
  • Fixed to use full minikube status exit code (returns non-zero when any component is unhealthy)
  • Simplified all downstream conditions to use exit code instead of string matching

Test plan

  • Verified the fix correctly skips minikube start when cluster is already fully running
  • Pre-commit hooks pass (ansible-lint, yamllint, etc.)

🤖 Generated with Claude Code

## Summary - After a power loss, minikube's Docker container (host) restarts but kubelet/apiserver remain stopped - The ansible role's status check used `--format='{{.Host}}'` which only examined the host VM state - When host=Running but kubelet/apiserver=Stopped, the role skipped `minikube start` - Fixed to use full `minikube status` exit code (returns non-zero when any component is unhealthy) - Simplified all downstream conditions to use exit code instead of string matching ## Test plan - [x] Verified the fix correctly skips `minikube start` when cluster is already fully running - [x] Pre-commit hooks pass (ansible-lint, yamllint, etc.) 🤖 Generated with [Claude Code](https://claude.com/claude-code)
After a power loss, minikube's Docker container (host) comes back up but
kubelet and apiserver remain stopped. The status check used
`--format='{{.Host}}'` which only examined the host state, causing the
role to skip `minikube start` since it saw "Running". Remove the format
flag so `minikube status` returns non-zero (exit 7) when any component
is unhealthy, and simplify all conditions to use the exit code alone.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eblume merged commit d76d675b29 into main 2026-02-09 23:03:01 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!137
No description provided.