Figured out what made that one node different from the rest: its UEFI network boot stack had both PXE and HTTP enabled, while the others were PXE only. After i added the kernel boot parameters, MAAS started to truncate the HTTP URI by a few characters (and now keeps doing that even if the kernel commandline options are cleared) which doesnt imapct the PXE clients but does break the HTTP ones (this node worked fine before the params were added).
For anyone stuck in this situation, the workaround seems to be to disable HTTP-based image acquisition in the system's BIOS configuration menu - PXE only on the IP stack desired will avoid the oddly truncated HTTP URI which occurs after setting kernel boot parameters. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950792 Title: No boot possible - Cannot open root device Status in MAAS: Triaged Status in linux package in Ubuntu: Incomplete Bug description: MaaS cannot boot on my X11DPi-NT and will therefore fail to commission. It will instantly fail after grub. It will fail to boot saying that is not able to open root device. I even tried supplying the squashfs via python on a different port as the url is somehow cut off a bit, but to no avail. The python webserver doesn't even see any connection try. ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs python webserver: python3 -m http.server 8080) Steps to reproduce: 1. Setup maas ;) 2. Try to commision server 3. See the kernel and initrd download fly by 4. Boom kernel panic Hardware: Supermicro X11DPi-NT with UEFI http Networkboot enabled NIC: Intel X722 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1950792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
