Juju fails to destroy-environment with wipe enabled: Node cannot be released in its current state ('Disk erasing').
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Using MAAS trunk (revision 3302) and juju 1.18.4+
To recreate:
- Configure MAAS to "Erase nodes' disks prior to releasing."
- Bootstrap an environment and wait until the bootstrap node is 'Deploying' (and has been booted up);
- Abort the bootstrap operation.
juju bootstrap
Launching instance
WARNING picked arbitrary tools &{"1.18.
- /MAAS/api/
Waiting for address
Attempting to connect to nuc2.maas:22
Attempting to connect to 192.168.10.75:22
^CInterrupt signalled: waiting for bootstrap to exit
ERROR bootstrap failed: interrupted
Stopping instance...
Bootstrap failed, destroying environment
ERROR Bootstrap failed, and the environment could not be destroyed: gomaasapi: got error back from server: 409 CONFLICT (Node cannot be released in its current state ('Disk erasing').)
ERROR interrupted
This is the apache log:
192.168.10.2 - - [27/Oct/
192.168.10.2 - - [27/Oct/
192.168.10.2 - - [27/Oct/
192.168.10.2 - - [27/Oct/
As you can see, the node is released *twice* and the second 'release' operation operates on a 'disk erasing' operation. That's the part that breaks.
Changed in maas: | |
milestone: | none → next |
summary: |
- Juju fails to destroy an environment: Node cannot be released in its - current state ('Disk erasing'). + Juju fails to destroy-environment with wipe enabled: Node cannot be + released in its current state ('Disk erasing'). |
Changed in maas: | |
milestone: | next → 1.7.1 |
Changed in maas: | |
milestone: | 1.7.1 → 1.7.2 |
Changed in maas: | |
milestone: | 1.7.2 → 1.7.3 |
Changed in maas: | |
status: | Incomplete → Won't Fix |
This is the same bug as bug 1384001 IMO. It's just that the disk erasing feature was enabled in MAAS so the state after DEPLOYED is different.