| 2020-05-16 00:53:49 |
Lee Trager |
bug |
|
|
added bug |
| 2020-05-16 00:54:04 |
Lee Trager |
bug task added |
|
shim-signed (Ubuntu) |
|
| 2020-05-16 00:54:27 |
Lee Trager |
bug task added |
|
grub (Ubuntu) |
|
| 2020-05-16 00:55:03 |
Lee Trager |
description |
When using MAAS to HTTP boot on x86_64 UEFI grub drops to the command line. net_ls_addr shows the system has no address. If I run net_dhcp I get an address. I can then download the remote grub.cfg file and continue boot.
When reproducing with QEMU you have to manually reconfigure the boot order to try HTTP before TFTP:
# efibootmgr -v
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0003,0001,0000,0004
Boot0000* UiApp FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* UEFI QEMU QEMU HARDDISK PciRoot(0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/SCSI(1,1)N.....YM....R,Y.
Boot0002* UEFI PXEv4 (MAC:00163E03BE1A) PciRoot(0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00163e03be1a,1)/IPv4(0.0.0.00.0.0.0,0,0)N.....YM....R,Y.
Boot0003* UEFI HTTPv4 (MAC:00163E03BE1A) PciRoot(0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00163e03be1a,1)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()N.....YM....R,Y.
Boot0004* EFI Internal Shell FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
# efibootmgr -o 0003,0002,0001,0004
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0003,0002,0001,0004
Boot0000* UiApp
Boot0001* UEFI QEMU QEMU HARDDISK
Boot0002* UEFI PXEv4 (MAC:00163E03BE1A)
Boot0003* UEFI HTTPv4 (MAC:00163E03BE1A)
Boot0004* EFI Internal Shell
grub> net_ls_addr
grub>
grub> net_dhcp
efinet0:dhcp 00:16:3e:03:be:1a 10.0.0.75
grub> configfile (http,10.0.0.2:5248)/grub/grub.cfg-default-amd64
Booting under MAAS direction...
I believe the bug is in grub or the shim. As MAAS receives its bootloaders from the stream at images.maas.io generated by lp:maas-images this effects all versions of MAAS. |
When using MAAS to HTTP boot on x86_64 UEFI grub drops to the command line. net_ls_addr shows the system has no address. If I run net_dhcp I get an address. I can then download the remote grub.cfg file and continue boot.
When reproducing with QEMU you have to manually reconfigure the boot order to try HTTP before TFTP:
# efibootmgr -v
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0003,0001,0000,0004
Boot0000* UiApp FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* UEFI QEMU QEMU HARDDISK PciRoot(0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/SCSI(1,1)N.....YM....R,Y.
Boot0002* UEFI PXEv4 (MAC:00163E03BE1A) PciRoot(0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00163e03be1a,1)/IPv4(0.0.0.00.0.0.0,0,0)N.....YM....R,Y.
Boot0003* UEFI HTTPv4 (MAC:00163E03BE1A) PciRoot(0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00163e03be1a,1)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()N.....YM....R,Y.
Boot0004* EFI Internal Shell FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
# efibootmgr -o 0003,0002,0001,0004
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0003,0002,0001,0004
Boot0000* UiApp
Boot0001* UEFI QEMU QEMU HARDDISK
Boot0002* UEFI PXEv4 (MAC:00163E03BE1A)
Boot0003* UEFI HTTPv4 (MAC:00163E03BE1A)
Boot0004* EFI Internal Shell
grub> net_ls_addr
grub>
grub> net_dhcp
efinet0:dhcp 00:16:3e:03:be:1a 10.0.0.75
grub> configfile (http,10.0.0.2:5248)/grub/grub.cfg-default-amd64
Booting under MAAS direction...
The kernel and initrd are downloaded but it hangs there.
I believe the bug is in grub or the shim. As MAAS receives its bootloaders from the stream at images.maas.io generated by lp:maas-images this effects all versions of MAAS. |
|
| 2020-05-16 08:43:28 |
Julian Andres Klode |
description |
When using MAAS to HTTP boot on x86_64 UEFI grub drops to the command line. net_ls_addr shows the system has no address. If I run net_dhcp I get an address. I can then download the remote grub.cfg file and continue boot.
When reproducing with QEMU you have to manually reconfigure the boot order to try HTTP before TFTP:
# efibootmgr -v
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0003,0001,0000,0004
Boot0000* UiApp FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* UEFI QEMU QEMU HARDDISK PciRoot(0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/SCSI(1,1)N.....YM....R,Y.
Boot0002* UEFI PXEv4 (MAC:00163E03BE1A) PciRoot(0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00163e03be1a,1)/IPv4(0.0.0.00.0.0.0,0,0)N.....YM....R,Y.
Boot0003* UEFI HTTPv4 (MAC:00163E03BE1A) PciRoot(0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00163e03be1a,1)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()N.....YM....R,Y.
Boot0004* EFI Internal Shell FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
# efibootmgr -o 0003,0002,0001,0004
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0003,0002,0001,0004
Boot0000* UiApp
Boot0001* UEFI QEMU QEMU HARDDISK
Boot0002* UEFI PXEv4 (MAC:00163E03BE1A)
Boot0003* UEFI HTTPv4 (MAC:00163E03BE1A)
Boot0004* EFI Internal Shell
grub> net_ls_addr
grub>
grub> net_dhcp
efinet0:dhcp 00:16:3e:03:be:1a 10.0.0.75
grub> configfile (http,10.0.0.2:5248)/grub/grub.cfg-default-amd64
Booting under MAAS direction...
The kernel and initrd are downloaded but it hangs there.
I believe the bug is in grub or the shim. As MAAS receives its bootloaders from the stream at images.maas.io generated by lp:maas-images this effects all versions of MAAS. |
When using MAAS to HTTP boot on x86_64 UEFI grub drops to the command line. net_ls_addr shows the system has no address. If I run net_dhcp I get an address. I can then download the remote grub.cfg file and continue boot.
When reproducing with QEMU you have to manually reconfigure the boot order to try HTTP before TFTP:
# efibootmgr -v
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0003,0001,0000,0004
Boot0000* UiApp FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* UEFI QEMU QEMU HARDDISK PciRoot(0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/SCSI(1,1)N.....YM....R,Y.
Boot0002* UEFI PXEv4 (MAC:00163E03BE1A) PciRoot(0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00163e03be1a,1)/IPv4(0.0.0.00.0.0.0,0,0)N.....YM....R,Y.
Boot0003* UEFI HTTPv4 (MAC:00163E03BE1A) PciRoot(0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00163e03be1a,1)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()N.....YM....R,Y.
Boot0004* EFI Internal Shell FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
# efibootmgr -o 0003,0002,0001,0004
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0003,0002,0001,0004
Boot0000* UiApp
Boot0001* UEFI QEMU QEMU HARDDISK
Boot0002* UEFI PXEv4 (MAC:00163E03BE1A)
Boot0003* UEFI HTTPv4 (MAC:00163E03BE1A)
Boot0004* EFI Internal Shell
grub> net_ls_addr
grub>
grub> net_dhcp
efinet0:dhcp 00:16:3e:03:be:1a 10.0.0.75
grub> configfile (http,10.0.0.2:5248)/grub/grub.cfg-default-amd64
Booting under MAAS direction...
The kernel and initrd are downloaded but it hangs there.
I believe the bug is in grub or the shim. As MAAS receives its bootloaders from the stream at images.maas.io generated by lp:maas-images this affects all versions of MAAS. |
|
| 2020-05-18 19:52:14 |
Lee Trager |
summary |
Shim does not hand off networking during HTTP boot |
GRUB does not bring up networking when loaded over HTTP |
|
| 2020-05-18 19:57:52 |
Lee Trager |
description |
When using MAAS to HTTP boot on x86_64 UEFI grub drops to the command line. net_ls_addr shows the system has no address. If I run net_dhcp I get an address. I can then download the remote grub.cfg file and continue boot.
When reproducing with QEMU you have to manually reconfigure the boot order to try HTTP before TFTP:
# efibootmgr -v
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0003,0001,0000,0004
Boot0000* UiApp FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* UEFI QEMU QEMU HARDDISK PciRoot(0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/SCSI(1,1)N.....YM....R,Y.
Boot0002* UEFI PXEv4 (MAC:00163E03BE1A) PciRoot(0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00163e03be1a,1)/IPv4(0.0.0.00.0.0.0,0,0)N.....YM....R,Y.
Boot0003* UEFI HTTPv4 (MAC:00163E03BE1A) PciRoot(0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00163e03be1a,1)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()N.....YM....R,Y.
Boot0004* EFI Internal Shell FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
# efibootmgr -o 0003,0002,0001,0004
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0003,0002,0001,0004
Boot0000* UiApp
Boot0001* UEFI QEMU QEMU HARDDISK
Boot0002* UEFI PXEv4 (MAC:00163E03BE1A)
Boot0003* UEFI HTTPv4 (MAC:00163E03BE1A)
Boot0004* EFI Internal Shell
grub> net_ls_addr
grub>
grub> net_dhcp
efinet0:dhcp 00:16:3e:03:be:1a 10.0.0.75
grub> configfile (http,10.0.0.2:5248)/grub/grub.cfg-default-amd64
Booting under MAAS direction...
The kernel and initrd are downloaded but it hangs there.
I believe the bug is in grub or the shim. As MAAS receives its bootloaders from the stream at images.maas.io generated by lp:maas-images this affects all versions of MAAS. |
When using MAAS to HTTP boot on x86_64 UEFI grub drops to the command line. net_ls_addr shows the system has no address. If I run net_dhcp I get an address. I can then download the remote grub.cfg file and continue boot.
When reproducing with QEMU you have to manually reconfigure the boot order to try HTTP before TFTP:
# efibootmgr -v
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0003,0001,0000,0004
Boot0000* UiApp FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* UEFI QEMU QEMU HARDDISK PciRoot(0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/SCSI(1,1)N.....YM....R,Y.
Boot0002* UEFI PXEv4 (MAC:00163E03BE1A) PciRoot(0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00163e03be1a,1)/IPv4(0.0.0.00.0.0.0,0,0)N.....YM....R,Y.
Boot0003* UEFI HTTPv4 (MAC:00163E03BE1A) PciRoot(0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00163e03be1a,1)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()N.....YM....R,Y.
Boot0004* EFI Internal Shell FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
# efibootmgr -o 0003,0002,0001,0004
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0003,0002,0001,0004
Boot0000* UiApp
Boot0001* UEFI QEMU QEMU HARDDISK
Boot0002* UEFI PXEv4 (MAC:00163E03BE1A)
Boot0003* UEFI HTTPv4 (MAC:00163E03BE1A)
Boot0004* EFI Internal Shell
grub> net_ls_addr
grub>
grub> net_dhcp
efinet0:dhcp 00:16:3e:03:be:1a 10.0.0.75
grub> configfile (http,10.0.0.2:5248)/grub/grub.cfg-default-amd64
Booting under MAAS direction...
The kernel and initrd are downloaded but it hangs there.
I believe the bug is in grub. As MAAS receives its bootloaders from the stream at images.maas.io generated by lp:maas-images this affects all versions of MAAS. Currently MAAS uses GRUB and the Shim from Bionic however I have been able to reproduce this bug using GRUB and the shim from Focal as well. |
|
| 2020-05-18 23:07:34 |
Steve Langasek |
affects |
grub (Ubuntu) |
grub2 (Ubuntu) |
|
| 2020-06-03 13:57:47 |
Dimitri John Ledkov |
shim-signed (Ubuntu): status |
New |
Incomplete |
|
| 2020-06-03 13:57:49 |
Dimitri John Ledkov |
grub2 (Ubuntu): status |
New |
Incomplete |
|
| 2020-06-04 02:53:28 |
Lee Trager |
grub2 (Ubuntu): status |
Incomplete |
New |
|
| 2020-06-04 02:53:30 |
Lee Trager |
shim-signed (Ubuntu): status |
Incomplete |
New |
|
| 2020-06-04 12:40:20 |
Alberto Donato |
maas: milestone |
2.8.0rc1 |
2.8.0 |
|
| 2020-06-11 07:24:42 |
Alberto Donato |
maas: milestone |
2.8.0rc3 |
2.8.0 |
|
| 2020-06-23 10:46:32 |
Alberto Donato |
maas: milestone |
2.8.0 |
2.9.0b1 |
|
| 2020-06-30 11:00:59 |
Adam Collard |
tags |
|
maas-grub |
|
| 2020-08-05 21:06:55 |
Launchpad Janitor |
grub2 (Ubuntu): status |
New |
Confirmed |
|
| 2020-08-05 21:06:55 |
Launchpad Janitor |
shim-signed (Ubuntu): status |
New |
Confirmed |
|
| 2020-09-08 23:41:09 |
Lee Trager |
maas: milestone |
2.9.0b1 |
2.9.0b2 |
|
| 2020-09-19 19:39:28 |
Lee Trager |
maas: milestone |
2.9.0b2 |
2.9.0b3 |
|
| 2020-09-19 19:41:52 |
Lee Trager |
maas: milestone |
2.9.0b3 |
2.9.0b4 |
|
| 2020-10-02 07:54:46 |
Björn Tillenius |
maas: status |
Confirmed |
Triaged |
|
| 2020-10-14 15:46:07 |
Matthieu Clemenceau |
tags |
maas-grub |
fr-683 maas-grub |
|
| 2020-10-16 19:22:53 |
Lee Trager |
maas: milestone |
2.9.0b4 |
2.9.0b7 |
|
| 2020-10-20 17:01:11 |
Adam Collard |
maas: milestone |
2.9.0b7 |
2.9.x |
|
| 2021-02-04 11:14:46 |
Adam Collard |
maas: milestone |
2.9.2 |
2.9.x |
|
| 2021-02-12 23:50:10 |
Dimitri John Ledkov |
shim-signed (Ubuntu): status |
Confirmed |
Invalid |
|
| 2021-02-12 23:50:12 |
Dimitri John Ledkov |
grub2 (Ubuntu): status |
Confirmed |
Fix Committed |
|
| 2022-08-25 08:40:46 |
Jerzy Husakowski |
maas: milestone |
2.9.x |
3.3.0 |
|
| 2022-10-20 10:46:07 |
Jerzy Husakowski |
maas: milestone |
3.3.0 |
3.4.0 |
|
| 2022-10-21 09:43:15 |
Olivier Gayot |
tags |
fr-683 maas-grub |
foundations-triage-discuss fr-683 maas-grub |
|
| 2023-04-20 08:41:24 |
Jerzy Husakowski |
maas: milestone |
3.4.0 |
3.5.0 |
|
| 2023-05-12 12:37:07 |
Jacopo Rota |
attachment added |
|
bug.mp4 https://bugs.launchpad.net/maas/+bug/1879012/+attachment/5672709/+files/bug.mp4 |
|
| 2024-03-01 09:40:29 |
Jerzy Husakowski |
maas: status |
Triaged |
Incomplete |
|
| 2024-03-01 09:40:29 |
Jerzy Husakowski |
maas: milestone |
3.5.0 |
|
|
