** Also affects: maas/2.9
Importance: Undecided
Status: New
** Changed in: maas/2.9
Status: New => Fix Committed
** Changed in: maas/2.9
Milestone: None => 2.9.3
** Also affects: maas/2.8
Importance: Undecided
Status: New
** Also affects: maas/2.7
Importance:
Good news everybody! False alarm - it seems to be working w/ 2.9.3-beta1
after waiting a bit. I was certain I had waited for images to sync
before testing (according to the UI), so not sure what was needed to
lock it in, but it does seem to be good.
--
You received this bug notification because
hm.. I don't have perms to reopen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
Title:
grubnet default grub.cfg should try /grub/grub.cfg-${net_default_mac}
before /grub/grub.cfg
To
I upgraded to 2.9.3~beta1 (9197-g.afe92bb63), which appears to have the
fix integrated, but I'm still seeing the same issue. That is, if I PXE
boot an unknown arm64 machine, it is given an arm64 GRUB configured to
boot amd64 files. I'm therefore reopening.
--
You received this bug notification
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
Title:
grubnet default grub.cfg should try /grub/grub.cfg-${net_default_mac}
** Merge proposal linked:
https://code.launchpad.net/~ltrager/maas/+git/maas/+merge/402538
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
Title:
grubnet default grub.cfg should try
** Merge proposal linked:
https://code.launchpad.net/~ltrager/maas/+git/maas/+merge/402464
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
Title:
grubnet default grub.cfg should try
On Wed, May 5, 2021 at 2:15 PM Lee Trager <1923...@bugs.launchpad.net> 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
** Merge proposal linked:
https://code.launchpad.net/~ltrager/maas/+git/maas/+merge/402288
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
Title:
grubnet default grub.cfg should try
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 associated branch
Unfortunately it appears this issue goes beyond just enlistment. I
manually added 6 new arm64 systems using the MAAS UI, and made sure I
set the architecture to "arm64/generic". They then automatically entered
commissioning mode. However, they are also failing to Commission. MAAS
shows "0/arm64"
** Changed in: maas
Status: New => Fix Committed
** Changed in: maas
Milestone: None => 3.0.0-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
Title:
grubnet default grub.cfg
Thanks for the quick turnaround on an MP @ltrager!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
Title:
grubnet default grub.cfg should try /grub/grub.cfg-${net_default_mac}
before
The attached MP should fix this in newer versions of MAAS. We still may
want to change the default grub.cfg for older versions of MAAS as I'm
not sure how far we will be backporting it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~ltrager/maas/+git/maas/+merge/402228
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
Title:
grubnet default grub.cfg should try
lp:maas-images produces the bootloaders stream. It was previously
pointed to Bionic for i386(pxelinux), amd64(shim+grub-signed), and
arm64(grub) while PPC64(grub) is pointed to Xenial. In an attempt to get
secure boot working I upgraded i386, amd64, and arm64 to Focal. arm64
and PPC64 had their
Understood, and I see you already covered that above. What I don't
follow is what caused MAAS enlistment of ARM to break. I mean, it used
to work fine. From reading the tea leaves here, was it that MAAS
switched from generating its own grubnet image w/ a built-in grub.cfg to
a signed (and
MAAS expects the Debian architecture to be used. We could create a map
for it and respond as you suggest. However this would only fix new
versions of MAAS. MAAS started using bootloaders from the stream in MAAS
2.1. We no longer support MAAS < 2.5, those versions would remain
broken. It would most
Couldn't MAAS generate a grub.cfg that dynamically determines the
appropriate fallback architecture?
grub> echo $grub_cpu
arm64
** Also affects: maas
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
When MAAS gets the TFTP/HTTP request for grub.cfg it doesn't know what
the client architecture is. MAAS identifies the machine based on the
requested URL. MAAS comes with a default grub.cfg[1] which tries loading
/grub/grub.cfg-${net_default_mac} and if that fails /grub/grub.cfg-
default-amd64.
Note that upstream and all distro grubs have moved on to query for:
"""
This patch implements a search for a specific configuration when the config
file is on a remoteserver. It uses the following order:
1) DHCP client UUID option.
2) MAC address (in lower case hexadecimal with dash
Can you please paste the contents of MAAS generated:
grub.cfg-default-amd64
grub.cfg-default-arm64
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
Title:
grubnet default grub.cfg should
Also i am kind of confused why there are different per-arch grub.cfg for
enlistment.
there is no reason to have different grub.cfg per arch, as inside the
grub.cfg that is served everything can be provided for all arches.
--
You received this bug notification because you are a member of Ubuntu
I am slightly confused what is being asked here.
The default grub.cfg that is built into grubnet comes from here:
https://git.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/tree/debian
/build-efi-images?h=ubuntu#n71
Can you please make a merge proposal with exactly what you are asking
for?
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2-signed (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
** Tags added: maas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
Title:
grubnet default grub.cfg should try /grub/grub.cfg-${net_default_mac}
before /grub/grub.cfg
To manage
We have noticed that this is breaking enlistment in MAAS on ARM64. Using
${grub_cpu} may work but MAAS expects Debian architectures.
[1] https://www.gnu.org/software/grub/manual/grub/grub.html#grub_005fcpu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
27 matches
Mail list logo
