On Wed, May 5, 2021 at 2:15 PM Lee Trager <email address hidden> wrote:
>
> When you added the ARM64 machine are you including the boot MAC address
> or just the IPMI credentials? When you add just the IPMI credentials the
> machine actually goes into enlistment but MAAS detects its a known
> machine based on IPMI credenitals when the BMC is detected.
The only MAC address I added was the BMC MAC - I didn't add any host
NIC MACs initially, so your explanation makes sense. Let me know if
it'd be helpful for you if I retested w/ host MACs though.
> The associated branch updates the default grub.cfg file which is stored
> with all boot images. These files only get updated when a new image is
> found on images.maas.io or whatever your mirror is. To force the update
> you can run
>
> sudo rm -rf /var/lib/maas/boot-resources/*
> sudo systemctl restart maas-rackd
Understood. We're still running a snap version, so I won't be able to
easily pick up a source code patch. We plan to switch back to a deb
install so we can be more agile in helping with testing patches, but
we haven't scheduled the downtime yet. I can always set up another
MAAS in the lab w/ debs if you need me to test something though.
On Wed, May 5, 2021 at 2:15 PM Lee Trager <email address hidden> wrote:
>
> When you added the ARM64 machine are you including the boot MAC address
> or just the IPMI credentials? When you add just the IPMI credentials the
> machine actually goes into enlistment but MAAS detects its a known
> machine based on IPMI credenitals when the BMC is detected.
The only MAC address I added was the BMC MAC - I didn't add any host
NIC MACs initially, so your explanation makes sense. Let me know if
it'd be helpful for you if I retested w/ host MACs though.
> The associated branch updates the default grub.cfg file which is stored maas/boot- resources/ *
> with all boot images. These files only get updated when a new image is
> found on images.maas.io or whatever your mirror is. To force the update
> you can run
>
> sudo rm -rf /var/lib/
> sudo systemctl restart maas-rackd
Understood. We're still running a snap version, so I won't be able to
easily pick up a source code patch. We plan to switch back to a deb
install so we can be more agile in helping with testing patches, but
we haven't scheduled the downtime yet. I can always set up another
MAAS in the lab w/ debs if you need me to test something though.
-dann