MAAS fails to release machine and provides no means to force release
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I recommissioned a machine and that broke because of issues around managing cipher suites.
But that left my machine in a failed state with a Power Error.
Alexsander suggested a commissioning script to re-enable the missing cipher suite to see if that fixes the underlying issue, however, to do that I need to trigger a commissioning again, and manually power the machine on.
BUT, maas refuses to release the machine (see screen shot) because of the power error.
The only real option from the Action menu is "Release" and that fails and there's no way to overrride or force the release that I can tell.
I could delete the machine, but that would then break our automation since deleting and recreating will mean the MAAS ID changes. I can't imagine this sort of scenario is unique.
So it would be nice if MAAS could override the power error complaints, and let me trigger a recommission and then manually power the machine on to run all the commissioning scripts (including the one that should restore disabled cipher suites).
| Jeff Lane (bladernr) wrote | #1 |
| Anton Troyanov (troyanov) wrote | #2 |
| Jeff Lane (bladernr) wrote | #3 |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Jerzy Husakowski (jhusakowski) wrote | #4 |
| Changed in maas: | |
| milestone: | none → 3.5.0 |
Hi Jeff,
Since MAAS is failing to configure BMC it won't be able to control machine power configuration.
In that case can you please try to change machine power configuration to manual?
That's under machine Configuration tab: Power configuration -> Power type -> Manual
Once it is set to manual MAAS should be able to release the machine and during recommissioning, it should set the power back to IPMI.