Comment 6 for bug 1851276

Thanks for the cloud-init logs. I did find some minor bugs in MAAS by looking at them. But even after reproducing those errors in the logs, the machine still commissioned ok, and I was able to use it.

So, I will need some more information. The first is the exact steps you do to reproduce the issue, e.g. how you add the machine to MAAS, what actions you take on it until you commission it.

Then I also need to know what errors you see in the MAAS UI. The output from 'maas $profile machine read $systemid' would be good.

Also, it seems that you have Xenial set as the commissioning environment. Could you go to the MAAS settings and change that to Bionic? That might help.

I also need all the logs from /var/log/maas from the machine where MAAS is installed.

For the MAAS developers, there's a minor bug in that when a machine doesn't have any disks, we generate network configuration for the node. This shouldn't be done on commmissioning, and it will also break on xenial deployments, since netplan isn't installed by default there. Yet the vendor data we produce tries to run 'netplan apply'. See src/metadataserver/vendor_data.py.