Can't recommission machines when IPMI password is incorrect

[Andreas Hasenack]

Due to unrelated issues, all machines that were in MAAS got their IPMI passwords reset. As a result, MAAS cannot drive their power anymore.

With MAAS 1.6, what I would do is to just select them all, hit "commission", and then power the machines up manually.

With MAAS 1.7, that's no longer possible, because MAAS will try to power them up with the password it knows, which no longer works, then fail, and mark the node as failed.

[Andres Rodriguez (andreserl)]

This means that if there's a node that failed because incorrect password, we should be able to re-commission the node to try to re-create passwords automatically , and be allowed to manually power on the node.

The robustness work should not interfere at all if this is the case. This seems that it is preventing re-commissioning all the time because MAAS sees the failed power request and prevents the user from manually power it on to actually make it recommission. We need to address this as this feels like a regression.

[Raphaël Badin (rvb)]

What you're seeing here is the correct behavior: if MAAS is in charge of powering a node up and can't do it because the credentials are wrong, it must mark the node as broken.

In MAAS 1.6, you were using the fact that MAAS didn't check if the power command was successful or not. I wouldn't call this a regression: the robustness work simply prevents you from using a workaround you were using in MAAS 1.6.

Now, I understand this is a problem for you and I think we should take a step back and see if we can't find a solution that would work for your use case without relaxing the assumption that MAAS is responsible for powering up and down the nodes in control.

[Andres Rodriguez (andreserl)]

Dear user,

This is an automated message.

We believe this bug report is no longer an issue in the latest version of MAAS. For such reason, we are making this issue as Won't Fix. If you believe this issue is still present in the latest version of MAAS, please re-open this bug report.