Node is stuck "exiting rescue mode" from failed deployment
Bug #1771777 reported by
Alberto Donato
This bug affects 17 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
Medium
|
Unassigned | ||
3.5 |
Won't Fix
|
Medium
|
Unassigned | ||
3.6 |
Triaged
|
Medium
|
Unassigned |
Bug Description
After a failed deployment, I put the node in rescue mode to access the curtin config.
This works, but when I try to exit rescue mode, the node is stuck in that state.
Looking at the code, it seems we don't handle the case where the previous state of the node was FAILED_DEPLOYMENT
What I did was:
- deploy a node
- deploy failed, so state is FAILED_DEPLOYMENt
- select "enter rescue mode" from the UI
- after checking the node via ssh, I selected "exit rescue mode"
description: | updated |
Changed in maas: | |
milestone: | 2.5.x → 2.5.0beta1 |
Changed in maas: | |
milestone: | 2.5.0beta1 → 2.5.0beta2 |
Changed in maas: | |
milestone: | 2.5.0beta2 → 2.5.0rc1 |
Changed in maas: | |
milestone: | 2.5.0rc1 → 2.5.0 |
Changed in maas: | |
milestone: | 2.5.0 → 2.5.x |
Changed in maas: | |
milestone: | 2.6.0 → none |
status: | Incomplete → Triaged |
summary: |
- [2.5] Node is stuck "exiting rescue mode" from failed deployment + Node is stuck "exiting rescue mode" from failed deployment |
Changed in maas: | |
importance: | High → Medium |
milestone: | none → 3.4.0 |
Changed in maas: | |
milestone: | 3.4.0 → 3.4.x |
Changed in maas: | |
milestone: | 3.4.x → 3.5.x |
To post a comment you must log in.
I've been able to reproduce the same issue, although i have not had any error logs. This may be a backend issue that we are not tracking correctly.