API doesn't indicate whether a node is deployable

[Björn Tillenius]

With MAAS 1.9, you can change disk layout, and if you for example mount a bcache partition on /, the UI will tell you that the node can't be deployed.

However, the API won't give you any indication that the node can't be deployed. This is a problem for the autopilot, since it should fail early rather than later. I don't think reimplementing the same logic as the MAAS UI uses would be a good idea. There should be a clear indication that the node can't be deployed.

A new status might be in order. IMHO a node shouldn't be consider READY if it can't be deployed.

[Andres Rodriguez (andreserl)]

Adding a new status is not something we will do for 1.9 as it affects the life cycle of the machine and that falls outside of the support we are providing to it.

That being said, a machine becomes ready after it has been commissioned. The users makes the mistake and MAAS correctly tells the user that the machine, while has been made ready by MAAS, it is not deployable. Provided that MAAS provided a Ready, deployable machine, but the user made it not deployable, I believe the right approach, for 1.9, would be to provide an API state that will tell whether the machine is deployable or not, within the Ready state.

[Andres Rodriguez (andreserl)]

We believe that this is not longer an issue in the latest releases of MAAS. If you believe this is still an issue, please re-open this bug report and target it accordingly.