Lunar fails to deploy via MAAS

[Jeff Lane ]

We need to be able to test dev releases and interims as well... so we use hte maas candidate stream for daily images.

Running MAAS 3.3.4, we have not been able to deploy lunar or mantic at all. Both seem to start booting and then drop to a busybox shell (observed through the BMC KVM console).

I've attached a brief video where you can see it trying to load the installer envrionment on Mantic and then dropping to a busybox shell... it seems to be complaining about not being able to find the network device it PXE booted on... so maybe there's a driver problem? But we have not been able to install this on any server from any vendor, and that includes a multitude of PXE boot NICs from Intel and Broadcom that all have the same issue.

The system in the video is booting from an Intel I350, so not a new, unknown device, this is a quite old and very well established network controller.

[Jeff Lane  (bladernr)]

This also applies to Mantic... Neither is deployable via MAAS, I tried both on the same three machines, one i350 based, one with an x550, and one with a Cisco VIC, same failures for both Lunar and Mantic on all three machines when trying to deploy.

[Francis Ginther (fginther)]

@bladernr, based on your symptoms and the date this was filed, I believe you ar hitting https://bugs.launchpad.net/maas/+bug/2016908. If it is, the workaround is to set a kernel command line parameter "apparmor=1". This is a known issue with kernel version 6.2.0-20.20.

Maas images were not being updated until Sept 10 (or 11th) with a newer kernel.

Mantic images were also not updated until Sept 10.

[Nick De Villiers (nickdv99)]

Marked this as "Won't fix" after discussion with @lloydwaltersj, since Lunar is no longer a supported release.