You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's currently not possible to determine the status of machines enlisted in MAAS to base workflows on the machine status. For instance, in this open issue where it's impossible to maintain idempotency in block storage configurations for MAAS-enlisted nodes, the workaround is to manually (local-exec) remove the filesystems, partitions, and disks from each node and then start from a clean slate to apply desired storage and network configurations. However, these operations require that the machines being actioned upon are all in Ready state. If even one node is in Error/Deployed (non-Ready) state, the resources (like maas_block_device or maas_network_interface_physical) error out and subsequent resources in the plan are never applied (rightfully so).
To avoid getting into this situation, it's necessary to filter enlisted machines based on their status, which is currently not exposed in the maas_machine datasource. It would be nice to have this field exposed to avoid complicated JSON-parsing with MAAS CLI command outputs.
The text was updated successfully, but these errors were encountered:
It's currently not possible to determine the status of machines enlisted in MAAS to base workflows on the machine status. For instance, in this open issue where it's impossible to maintain idempotency in block storage configurations for MAAS-enlisted nodes, the workaround is to manually (local-exec) remove the filesystems, partitions, and disks from each node and then start from a clean slate to apply desired storage and network configurations. However, these operations require that the machines being actioned upon are all in Ready state. If even one node is in Error/Deployed (non-Ready) state, the resources (like
maas_block_device
ormaas_network_interface_physical
) error out and subsequent resources in the plan are never applied (rightfully so).To avoid getting into this situation, it's necessary to filter enlisted machines based on their status, which is currently not exposed in the
maas_machine
datasource. It would be nice to have this field exposed to avoid complicated JSON-parsing with MAAS CLI command outputs.The text was updated successfully, but these errors were encountered: