I looked at the logging from the new run, and it seems like a race condition of some type. We rebooted one of the machines that failed commissioning, and then observed it working.
In the new logs, there is still no console logging - but not because console logging wasn't turned on. It was because the machines failed to boot from the network, and thus failed to do anything at all besides idle on a "No bootable device" screen.
I'd like to understand the order of operations here; it could be the machines are being composed too soon, or it could be that MAAS didn't bring up its services in a timely manner.
I looked at the logging from the new run, and it seems like a race condition of some type. We rebooted one of the machines that failed commissioning, and then observed it working.
In the new logs, there is still no console logging - but not because console logging wasn't turned on. It was because the machines failed to boot from the network, and thus failed to do anything at all besides idle on a "No bootable device" screen.
I'd like to understand the order of operations here; it could be the machines are being composed too soon, or it could be that MAAS didn't bring up its services in a timely manner.