[Kernel-packages] [Bug 1790586] Re: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system
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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790586 Title: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system Status in ubuntu-kernel-tests: Invalid Status in grub2 package in Ubuntu: Expired Status in linux package in Ubuntu: Invalid Bug description: Similar to bug 1642298, bug 1750732 and bug 1788539 This issue was only spotted on ThunderX Cavium ARM64 system and an AMD Naples amd64 server in this SRU cycle. Steps: 1. Deploy the ThunderX system with Trusty + T-LTS 4.4 kernel (It works fine with just Trusty, however this was tested on the AMD Naples, not ThunderX since it does not support 3.13 kernel) 2. Check the efibootmgr output 3. Enable proposed, install grub-common 4. Check efibootmgr again Result: In step 2, the boot order is correct: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: 0002,,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC But in step 4, the boot order will be overridden: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: ,0002,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: grub-common 2.02~beta2-9ubuntu1.15 ProcVersionSignature: User Name 4.4.0-134.160~14.04.1-generic 4.4.140 Uname: Linux 4.4.0-134-generic aarch64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: arm64 Date: Tue Sep 4 07:45:19 2018 SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1790586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790586] Re: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790586 Title: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system Status in ubuntu-kernel-tests: Incomplete Status in grub2 package in Ubuntu: Expired Status in linux package in Ubuntu: Invalid Bug description: Similar to bug 1642298, bug 1750732 and bug 1788539 This issue was only spotted on ThunderX Cavium ARM64 system and an AMD Naples amd64 server in this SRU cycle. Steps: 1. Deploy the ThunderX system with Trusty + T-LTS 4.4 kernel (It works fine with just Trusty, however this was tested on the AMD Naples, not ThunderX since it does not support 3.13 kernel) 2. Check the efibootmgr output 3. Enable proposed, install grub-common 4. Check efibootmgr again Result: In step 2, the boot order is correct: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: 0002,,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC But in step 4, the boot order will be overridden: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: ,0002,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: grub-common 2.02~beta2-9ubuntu1.15 ProcVersionSignature: User Name 4.4.0-134.160~14.04.1-generic 4.4.140 Uname: Linux 4.4.0-134-generic aarch64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: arm64 Date: Tue Sep 4 07:45:19 2018 SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1790586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790586] Re: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system
[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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790586 Title: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system Status in ubuntu-kernel-tests: Incomplete Status in grub2 package in Ubuntu: Expired Status in linux package in Ubuntu: Invalid Bug description: Similar to bug 1642298, bug 1750732 and bug 1788539 This issue was only spotted on ThunderX Cavium ARM64 system and an AMD Naples amd64 server in this SRU cycle. Steps: 1. Deploy the ThunderX system with Trusty + T-LTS 4.4 kernel (It works fine with just Trusty, however this was tested on the AMD Naples, not ThunderX since it does not support 3.13 kernel) 2. Check the efibootmgr output 3. Enable proposed, install grub-common 4. Check efibootmgr again Result: In step 2, the boot order is correct: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: 0002,,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC But in step 4, the boot order will be overridden: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: ,0002,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: grub-common 2.02~beta2-9ubuntu1.15 ProcVersionSignature: User Name 4.4.0-134.160~14.04.1-generic 4.4.140 Uname: Linux 4.4.0-134-generic aarch64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: arm64 Date: Tue Sep 4 07:45:19 2018 SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1790586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790586] Re: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system
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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790586 Title: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system Status in ubuntu-kernel-tests: Incomplete Status in grub2 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: Similar to bug 1642298, bug 1750732 and bug 1788539 This issue was only spotted on ThunderX Cavium ARM64 system and an AMD Naples amd64 server in this SRU cycle. Steps: 1. Deploy the ThunderX system with Trusty + T-LTS 4.4 kernel (It works fine with just Trusty, however this was tested on the AMD Naples, not ThunderX since it does not support 3.13 kernel) 2. Check the efibootmgr output 3. Enable proposed, install grub-common 4. Check efibootmgr again Result: In step 2, the boot order is correct: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: 0002,,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC But in step 4, the boot order will be overridden: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: ,0002,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: grub-common 2.02~beta2-9ubuntu1.15 ProcVersionSignature: User Name 4.4.0-134.160~14.04.1-generic 4.4.140 Uname: Linux 4.4.0-134-generic aarch64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: arm64 Date: Tue Sep 4 07:45:19 2018 SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1790586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790586] Re: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system
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 it can be reproduced after removing the 0004 boot entry? sudo efibootmgr -b -B 0004 ** Changed in: grub2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790586 Title: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system Status in ubuntu-kernel-tests: Confirmed Status in grub2 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: Similar to bug 1642298, bug 1750732 and bug 1788539 This issue was only spotted on ThunderX Cavium ARM64 system and an AMD Naples amd64 server in this SRU cycle. Steps: 1. Deploy the ThunderX system with Trusty + T-LTS 4.4 kernel (It works fine with just Trusty, however this was tested on the AMD Naples, not ThunderX since it does not support 3.13 kernel) 2. Check the efibootmgr output 3. Enable proposed, install grub-common 4. Check efibootmgr again Result: In step 2, the boot order is correct: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: 0002,,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC But in step 4, the boot order will be overridden: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: ,0002,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: grub-common 2.02~beta2-9ubuntu1.15 ProcVersionSignature: User Name 4.4.0-134.160~14.04.1-generic 4.4.140 Uname: Linux 4.4.0-134-generic aarch64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: arm64 Date: Tue Sep 4 07:45:19 2018 SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1790586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790586] Re: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system
Not a kernel bug. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790586 Title: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system Status in ubuntu-kernel-tests: Confirmed Status in grub2 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: Similar to bug 1642298, bug 1750732 and bug 1788539 This issue was only spotted on ThunderX Cavium ARM64 system and an AMD Naples amd64 server in this SRU cycle. Steps: 1. Deploy the ThunderX system with Trusty + T-LTS 4.4 kernel (It works fine with just Trusty, however this was tested on the AMD Naples, not ThunderX since it does not support 3.13 kernel) 2. Check the efibootmgr output 3. Enable proposed, install grub-common 4. Check efibootmgr again Result: In step 2, the boot order is correct: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: 0002,,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC But in step 4, the boot order will be overridden: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: ,0002,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: grub-common 2.02~beta2-9ubuntu1.15 ProcVersionSignature: User Name 4.4.0-134.160~14.04.1-generic 4.4.140 Uname: Linux 4.4.0-134-generic aarch64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: arm64 Date: Tue Sep 4 07:45:19 2018 SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1790586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790586] Re: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system
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 2.02-2ubuntu8.4
grub-pc-bin 2.02-2ubuntu8.4
grub2-common 2.02-2ubuntu8.4
ubuntu@lodygin:~$ uname -a
Linux lodygin 4.15.0-35-generic #38-Ubuntu SMP Wed Sep 12 10:38:24 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Changed in: ubuntu-kernel-tests
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1790586
Title:
The proposed grub package in Trusty / Bionic overrides the boot order
on a MaaS deployed system
Status in ubuntu-kernel-tests:
Confirmed
Status in grub2 package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
Similar to bug 1642298, bug 1750732 and bug 1788539
This issue was only spotted on ThunderX Cavium ARM64 system and an AMD
Naples amd64 server in this SRU cycle.
Steps:
1. Deploy the ThunderX system with Trusty + T-LTS 4.4 kernel (It works fine
with just Trusty, however this was tested on the AMD Naples, not ThunderX since
it does not support 3.13 kernel)
2. Check the efibootmgr output
3. Enable proposed, install grub-common
4. Check efibootmgr again
Result:
In step 2, the boot order is correct:
ubuntu@wright-kernel:~$ sudo efibootmgr
BootCurrent: 0002
Timeout: 10 seconds
BootOrder: 0002,,0003,0004,0001
Boot* ubuntu
Boot0001 UEFI: Built-in EFI Shell
Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA
Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB
Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC
But in step 4, the boot order will be overridden:
ubuntu@wright-kernel:~$ sudo efibootmgr
BootCurrent: 0002
Timeout: 10 seconds
BootOrder: ,0002,0003,0004,0001
Boot* ubuntu
Boot0001 UEFI: Built-in EFI Shell
Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA
Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB
Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: grub-common 2.02~beta2-9ubuntu1.15
ProcVersionSignature: User Name 4.4.0-134.160~14.04.1-generic 4.4.140
Uname: Linux 4.4.0-134-generic aarch64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: arm64
Date: Tue Sep 4 07:45:19 2018
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1790586/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790586] Re: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system
>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: 0002,0003,0004,,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC ubuntu@lodygin:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 1 seconds BootOrder: 0002,,0003,0004 Boot* ubuntu Boot0002* UEFI: IP4 Intel(R) Gigabit CT Desktop Adapter Boot0003* UEFI: Built-in EFI Shell Boot0004* Hard Drive The only difference is that the grub package from proposed will change the boot order only on the AMD server: ubuntu@lodygin:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 1 seconds BootOrder: ,0002,0003,0004 Boot* ubuntu Boot0002* UEFI: IP4 Intel(R) Gigabit CT Desktop Adapter Boot0003* UEFI: Built-in EFI Shell Boot0004* Hard Drive -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790586 Title: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Similar to bug 1642298, bug 1750732 and bug 1788539 This issue was only spotted on ThunderX Cavium ARM64 system and an AMD Naples amd64 server in this SRU cycle. Steps: 1. Deploy the ThunderX system with Trusty + T-LTS 4.4 kernel (It works fine with just Trusty, however this was tested on the AMD Naples, not ThunderX since it does not support 3.13 kernel) 2. Check the efibootmgr output 3. Enable proposed, install grub-common 4. Check efibootmgr again Result: In step 2, the boot order is correct: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: 0002,,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC But in step 4, the boot order will be overridden: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: ,0002,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: grub-common 2.02~beta2-9ubuntu1.15 ProcVersionSignature: User Name 4.4.0-134.160~14.04.1-generic 4.4.140 Uname: Linux 4.4.0-134-generic aarch64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: arm64 Date: Tue Sep 4 07:45:19 2018 SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1790586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790586] Re: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system
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 member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790586 Title: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Similar to bug 1642298, bug 1750732 and bug 1788539 This issue was only spotted on ThunderX Cavium ARM64 system and an AMD Naples amd64 server in this SRU cycle. Steps: 1. Deploy the ThunderX system with Trusty + T-LTS 4.4 kernel (It works fine with just Trusty, however this was tested on the AMD Naples, not ThunderX since it does not support 3.13 kernel) 2. Check the efibootmgr output 3. Enable proposed, install grub-common 4. Check efibootmgr again Result: In step 2, the boot order is correct: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: 0002,,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC But in step 4, the boot order will be overridden: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: ,0002,0003,0004,0001 Boot* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: grub-common 2.02~beta2-9ubuntu1.15 ProcVersionSignature: User Name 4.4.0-134.160~14.04.1-generic 4.4.140 Uname: Linux 4.4.0-134-generic aarch64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: arm64 Date: Tue Sep 4 07:45:19 2018 SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1790586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
