A failed deployment cannot be fixed using Rescue mode

[Michael Iatrou]

maas 2.1.3+bzr5573-0ubuntu1~16.04.1

Steps to reproduce:

1. Deploy under conditions that guarantee a "Failed deployment" end state (e.g. deploy CentOS 7 on a UEFI enabled machine)
2. When the machine is marked as "Failed deployment", try to put it in Rescue Mode.

Observed behavior: An error shows up "1 node cannot be rescue mode. To proceed, update your selection."
Expected behavior: The machine should boot in Rescue Mode.

Note: the same behavior is observed independently of the power state of the machine that failed to deploy.

According to the documentation:

"Rescue mode - Boot a node ephemerally (Ubuntu running in memory on the underlying machine). This allows a user SSH to the machine for maintenance purposes. This can be done for a Deployed or Broken node as well as for a node that failed to deploy."

The documentation reflects the expected user experience, so this is considered a MAAS bug, not a documentation bug :)

The issue is consistently reproducible, happy to provide any logs and configuration details as needed.

Output from dpkg -l '*maas*' http://paste.ubuntu.com/24335257/

[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