Didn't see this anymore, and as lodygin is dead, I am closing this bug.
** Changed in: ubuntu-kernel-tests
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790586
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790586
Title:
The proposed grub package in Trusty / Bionic overrides the boot order
on a MaaS deployed system
To manage
[Expired for grub2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790586
Node lodygin is out-of-order now, need to check this later.
** Changed in: ubuntu-kernel-tests
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790586
Title:
Not a kernel bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790586
Title:
The proposed grub package in Trusty / Bionic
My guess is lodygin fails to boot from the network, and cycles all the
way to booting from Hard drive (0004), in which case, since shim and
everything really /are/ installed on disk, it gets run to recreate the
missing "ubuntu" entry.
Assuming you can reproduce this issue easily, can you check if
For the AMD node lodygin, I can see this issue again in this cycle with
Bionic
ubuntu@lodygin:~$ dpkg -l | grep grub | awk '{print$2,$3}'
grub-common 2.02-2ubuntu8.4
grub-efi-amd64 2.02-2ubuntu8.4
grub-efi-amd64-bin 2.02-2ubuntu8.4
grub-efi-amd64-signed 1.93.5+2.02-2ubuntu8.4
grub-pc
>From this point I don't think this is a dup as I can see the "ubuntu"
entry for both of the AMD Naples amd64 server and the TunderX arm64
server, with Bionic:
efibootmgr output after they have been deployed:
ubuntu@wright-kernel:~$ sudo efibootmgr
BootCurrent: 0002
Timeout: 10 seconds
BootOrder:
In theory, you should *never* have an "ubuntu" entry in efibootmgr when
MAAS-deployed. I'm guessing this is a dup of the following bug, for which a fix
has not been backported to trusty:
https://bugs.launchpad.net/maas/+bug/1642298
--
You received this bug notification because you are a
