Avoid shutting down (or rebooting) when we encounter critical failures during enlistment, commissioning and installation

[Christian Reis]

We currently always shut down (or reboot) a machine when enlistment, commissioning or deployment fail. However, that's hardly very useful, as the failure would be much more easily debugged in the running image.

For commissioning we currently allow the user to toggle remote access, but that normally causes you to waste a boot cycle if you run into a problem, since the pattern is to try to commission -> fail -> commission again, this time enabling the checkbox. If we just kept the machine on and enabled console/remote access then there would be no need to waste that time.

This would be useful in combination with bug 1621062 which requests enabling console login during commissioning.

[Christian Reis (kiko)]

Note that a very long timeout (15 mins?) for the first login would also be acceptable.

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team