Open jnummelin opened 8 months ago
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
Before creating an issue, make sure you've checked the following:
Platform
Version
v1.28.5
Sysinfo
`k0s sysinfo`
What happened?
Applying autopilot
Plan
with e.g. a wrong SHA for k0s binary makes it stall. Even if user re-applies with a correct SHA it's still "stuck" on failed state.The steps to workaround:
ControlNode
sDocs do not really say anything how to recover from these kinds of cases. 😞
Steps to reproduce
Plan
with a wrong SHA for k0s downloadPlan
getting to failed statePlan
still being in failed stateExpected behavior
Re-applying with a correct SHA should make autopilot to proceed. Autopilot should be able to figure out the
Plan
is modified and re-trigger the signalling for failed nodes. Maybe we could add the planresourceVersion
into the signalling data so AP can figure out if it should re-trigger the failed signal?Actual behavior
No response
Screenshots and logs
The
Additional context
No response