Hi,
I was also affected by this issue - to PXE boot at UEFI for add-on adapter i350
1Gb interface. Upgrading the MAAS server version to 18.04 bionic release did
not solve the symptom. But I was able to find a workaround by booting first the
IPv6 before IPv4 - the same workaround mentioned by Rod
This is already fixed in bionic / artful (given that it's landed there
as of grub2 2.02~beta3-4ubuntu6).
What is missing is landing the fixes for Xenial and possibly Trusty?
I can prepare the SRU for Trusty right now, but the one for Xenial will
be temporarily blocked by a shim update which just
This is a three year old bug that is still causing issues when booting
certain systems in MAAS. My understanding is that this is fixable/fixed
in Grub2 upstream (per Andres comments), so what do we need to do to fix
this in 14.04 and 16.04? I presume 18.04 won't be affected... is that
true?
Hopef
@cyphermox, any update on this? I believe we have run into this in the
field as well with a customer lab doing certification testing for
16.04.3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437024
@Mathieu is this a grub package only problem that can be SRU'd
relatively easy, or is it something more complicated that will really
require respins (and probably not be released until 16.04.4)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Mathieu, I've tested on all three affected servers in our possession
(jolteon, ostwald, and moltres), and the grubnetx64.efi.signed binary
works on all of them (delivered via the MAAS server, of course). Thanks
for this fix!
I've also tested on three systems that did not have this problem
(wildora
Actually, nevermind that. The files would not be signed correctly to
work with Secure Boot (at least, not without more fiddling).
Please use
http://archive.ubuntu.com/ubuntu/dists/artful/main/uefi/grub2-amd64/2.02~beta3-4ubuntu6/grubnetx64.efi.signed
, using that file from artful (to replace your
Mathieu, how would I install this? As I understand it, I'd need to
replace /var/lib/maas/boot-resources/current/grubx64.efi on the MAAS
server with a GRUB built for network booting, but it's unclear to me in
which of those packages a suitable file exists.
--
You received this bug notification bec
You could try
https://launchpad.net/~cyphermox/+archive/ubuntu/efi/+sourcepub/8195249
/+listing-archive-extra; it's a build of grub2 as it is in xenial, plus
the two needed patches to cover this weird firmware. I'll prepare proper
uploads for this tomorrow.
--
You received this bug notification b
Another update on this:
I updated jolteon (the Lenovo x3550 M5 that was the original source of
this bug report) with the latest firmware I could find (v.2.21, build
TBE126Q, dated 2016-11-18) and reproduced the original bug. It appears
to be unchanged, with one twist: At one point, the system was
Is there any progress on this? I'm encountering similar problems on at
least two more systems now (moltres and ostwald, which are Quanta S910
X31E and Supermicro SYS-6018R-WTR servers, respectively). I've managed
to find a working firmware setup to get the Quanta booting reliably, but
the Supermicr
I've talked to ivoks over IRC, and he confirmed that this is a firmware
issue rather than a MAAS issue.
He also mentioned that grub can address the issue and there's a patch
available for upstream.
As such, I've added 'grub2' as an affected package and marking this bug
as 'Invalid' in MAAS.
** A
Yes I will need to modify MAAS to debug the issue.
Next week works fine for me, as I am also stuck on doing other stuff
this week.
** No longer affects: grub2 (Ubuntu)
** Tags removed: grubnet
** Tags added: ipv6
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Yes, we can give you access, but that may have to wait until next week.
(I'm running certification tests on it now, and they'll go on until
sometime mid-afternoon.) If you'll want to change the MAAS
configuration, we'll probably want to move it from maaster to landmaas.
--
You received this bug n
This one might be more related to how we handle ipv6 on the tftp server.
With this stack trace here:
http://pastebin.ubuntu.com/10689385/
Would it be possible to gain access to the MAAS and machine to debug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This seems to be very similar to bug 1437353, targeting to grub2 as
well.
** Tags added: grubnet hwe
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => High
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
You receiv
16 matches
Mail list logo
