[Xenial] a4 - ARM64 nodes fail to restart during deployment causing them to fail

[Ryan Collis]

Our APM ARM64 nodes are no longer able to deploy. We have a blend of uboot and uefi based physical APM nodes as well as virt nodes running on physical APM machines. As of yesterday all of our ARM64 node began failing deployment. The node gets as far as "reboot: restarting system" (after a very long pause} and never actually restart. Manual restart results in the node booting into enlistment. This has been observed with both release and daily images and with fresh installs of 2.0a3 and 2.0a4. Our x86 systems are all deploying as expected. Nodes have been reenlisted and commissioned but still fail to deploy.

dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-=====================================-============-=============================================
ii maas 2.0.0~alpha4+bzr4824-0ubuntu1~xenial1 all MAAS server all-in-one metapackage
ii maas-cli 2.0.0~alpha4+bzr4824-0ubuntu1~xenial1 all MAAS command line API tool
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.0.0~alpha4+bzr4824-0ubuntu1~xenial1 all MAAS server common files
ii maas-dhcp 2.0.0~alpha4+bzr4824-0ubuntu1~xenial1 all MAAS DHCP server
ii maas-dns 2.0.0~alpha4+bzr4824-0ubuntu1~xenial1 all MAAS DNS server
ii maas-proxy 2.0.0~alpha4+bzr4824-0ubuntu1~xenial1 all MAAS Caching Proxy
ii maas-rack-controller 2.0.0~alpha4+bzr4824-0ubuntu1~xenial1 all MAAS server cluster controller
ii maas-region-controller 2.0.0~alpha4+bzr4824-0ubuntu1~xenial1 all MAAS server complete region controller
ii maas-region-controller-min 2.0.0~alpha4+bzr4824-0ubuntu1~xenial1 all MAAS Server minimum region controller
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.0.0~alpha4+bzr4824-0ubuntu1~xenial1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.0.0~alpha4+bzr4824-0ubuntu1~xenial1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.0.0~alpha4+bzr4824-0ubuntu1~xenial1 all MAAS server provisioning libraries (Python 3)

[Ryan Collis (vyan)]

correction: release images are deploying correctly

[Andres Rodriguez (andreserl)]

Hi Ryan,

Can you please attach the installation log of the machine itself, which is on the node details page. Also, any chance you can attach a console log from start to finish to see what you really mean?

Also, what does it mean reelase images are deploying correctly in comparison to what was reported in the bug?

[Ryan Collis (vyan)]

Hi Andres:
  As of this morning the physical nodes are deploying fine with the release images. I am going to deploy with the daily images and report back with the console logs you asked for.

[Andres Rodriguez (andreserl)]

Thanks Ryan!