@axino
I'm tried the default grub, which appears to be the one synced from maas.io stream which is in fact bionic-updates grub 2.02 signed net x64 efi app.
I have downloaded the hirsute 2.04 signed net x64 efi app and replaced it at
/var/snap/maas/common/maas/boot-resources/snapshot-20210112-205807/bootloader/uefi/amd64/grubx64.efi
(there are many other files called that, which ultimately after all symlinks point there)
then i also unsquashfs maas snap, and changed the templates to echo the full version number of grub on boot.
Specifically tweaked
./lib/python3.8/site-packages/provisioningserver/templates/uefi/config.local.amd64.template
to have:
echo "XNOX... ${package_version}"
Then deployed machines whilst monitoring the console over BMC to confirm that deployments happen with XNOX... 2.04-1ubuntu37
I wonder if i'm using some other NIC? I see on my ps5 nodes that there are 5 NICs available and pxe is configured for me over eno1 1 Gbps link.
@axino
I'm tried the default grub, which appears to be the one synced from maas.io stream which is in fact bionic-updates grub 2.02 signed net x64 efi app.
I have downloaded the hirsute 2.04 signed net x64 efi app and replaced it at
/var/snap/ maas/common/ maas/boot- resources/ snapshot- 20210112- 205807/ bootloader/ uefi/amd64/ grubx64. efi
(there are many other files called that, which ultimately after all symlinks point there)
then i also unsquashfs maas snap, and changed the templates to echo the full version number of grub on boot.
Specifically tweaked
./lib/python3. 8/site- packages/ provisioningser ver/templates/ uefi/config. local.amd64. template
to have:
echo "XNOX... ${package_version}"
Then deployed machines whilst monitoring the console over BMC to confirm that deployments happen with XNOX... 2.04-1ubuntu37
I wonder if i'm using some other NIC? I see on my ps5 nodes that there are 5 NICs available and pxe is configured for me over eno1 1 Gbps link.