| 2013-09-23 23:00:18 |
Steve Langasek |
bug |
|
|
added bug |
| 2013-09-23 23:17:51 |
Steve Langasek |
grub2 (Ubuntu): importance |
Undecided |
High |
|
| 2013-09-23 23:17:58 |
Steve Langasek |
grub2 (Ubuntu): milestone |
|
ubuntu-14.04 |
|
| 2013-10-11 02:34:58 |
Launchpad Janitor |
grub2 (Ubuntu): status |
New |
Confirmed |
|
| 2015-03-13 19:11:26 |
Steve Langasek |
grub2 (Ubuntu): milestone |
ubuntu-14.04 |
|
|
| 2015-06-10 19:22:42 |
Tom Eichhorn |
bug |
|
|
added subscriber Tom Eichhorn |
| 2016-04-27 23:42:37 |
Mike Pontillo |
bug |
|
|
added subscriber Mike Pontillo |
| 2016-05-19 00:26:21 |
Mathieu Trudel-Lapierre |
grub2 (Ubuntu): status |
Confirmed |
In Progress |
|
| 2016-05-19 00:26:24 |
Mathieu Trudel-Lapierre |
grub2 (Ubuntu): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2016-05-19 00:30:06 |
Andres Rodriguez |
bug |
|
|
added subscriber Andres Rodriguez |
| 2016-07-29 08:03:18 |
Launchpad Janitor |
grub2 (Ubuntu): status |
In Progress |
Fix Released |
|
| 2016-07-29 09:13:31 |
Steve Langasek |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-07-29 09:13:31 |
Steve Langasek |
bug task added |
|
grub2 (Ubuntu Xenial) |
|
| 2016-07-29 09:13:42 |
Steve Langasek |
grub2 (Ubuntu Xenial): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2016-07-29 09:13:44 |
Steve Langasek |
grub2 (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2016-07-29 09:13:48 |
Steve Langasek |
grub2 (Ubuntu Xenial): status |
New |
Triaged |
|
| 2016-08-03 19:58:42 |
Mathieu Trudel-Lapierre |
description |
Testing using the pre-built grubnetx64.efi, I am not able to use the tftp client support within grub2 to load configs (/kernels/initrds) over the network. This works fine if using IPv4.
grubnetx64.efi is being loaded over the network (via shim no less), so the firmware's network stack is definitely up and working. But when grub tries to load grub.cfg via the default path, it fails with:
error: couldn't send network packet.
This message is repeated, approximately once every three seconds. It looks to be an infinite loop; at least, the message is repeated more than 100 times. But sometimes, when I've not been paying close attention to the boot, I get a grub shell instead. In that case, the grub shell shows:
grub> echo $root
tftp,0.5.0.24
grub> set
[...]
net_default_server=
net_efinet2_boot_file=8:23f::2]/bootx64.efi
net_efinet2_ip=0.0.0.0
net_efinet2_mac=02:3f:00:00:00:00
[...]
prefix=(tftp,0.5.0.24)/grub
pxe_default_server=
root=tftp,0.5.0.24
[...]
grub>
The actual server IP is 2001:1938:23f::2.
I've booted a locally-generated (self-signed) grubnetx64.efi with grub-bootstrap.cfg modified to call 'set' first, and I get identical output for all of the network-related variables. |
[Impact]
Trying to PXE boot (with UEFI) over IPv6 with grub. This is especially relevant for MAAS users in IPv6 setups.
[Test cases]
0) Setup PXE boot infrastructure (https://wiki.ubuntu.com/UEFI/SecureBoot-PXE-IPv6, also https://github.com/openSUSE/kiwi/wiki/Setup-PXE-boot-with-EFI-Using-GRUB2 contains relevant information)
1) Attempt to PXE boot (with UEFI) over IPv6 a system.
Testers can use grubnetx64.efi.signed from http://archive.ubuntu.com/ubuntu/dists/xenial-proposed/main/uefi/grub2-amd64/current/ once the package is available in proposed.
[Regression potential]
Possible regressions include any issues in routing IPv4 or IPv6 and/or retrieving files over PXE/tftp via grub. Ping is a good way to validate that routing is being done correctly, so is actually booting using the build grubnetx64.efi.
---
Testing using the pre-built grubnetx64.efi, I am not able to use the tftp client support within grub2 to load configs (/kernels/initrds) over the network. This works fine if using IPv4.
grubnetx64.efi is being loaded over the network (via shim no less), so the firmware's network stack is definitely up and working. But when grub tries to load grub.cfg via the default path, it fails with:
error: couldn't send network packet.
This message is repeated, approximately once every three seconds. It looks to be an infinite loop; at least, the message is repeated more than 100 times. But sometimes, when I've not been paying close attention to the boot, I get a grub shell instead. In that case, the grub shell shows:
grub> echo $root
tftp,0.5.0.24
grub> set
[...]
net_default_server=
net_efinet2_boot_file=8:23f::2]/bootx64.efi
net_efinet2_ip=0.0.0.0
net_efinet2_mac=02:3f:00:00:00:00
[...]
prefix=(tftp,0.5.0.24)/grub
pxe_default_server=
root=tftp,0.5.0.24
[...]
grub>
The actual server IP is 2001:1938:23f::2.
I've booted a locally-generated (self-signed) grubnetx64.efi with grub-bootstrap.cfg modified to call 'set' first, and I get identical output for all of the network-related variables. |
|
| 2016-08-03 19:58:48 |
Mathieu Trudel-Lapierre |
grub2 (Ubuntu Xenial): status |
Triaged |
In Progress |
|
| 2016-08-03 20:55:33 |
Mathieu Trudel-Lapierre |
bug task added |
|
grub2-signed (Ubuntu) |
|
| 2016-08-03 20:56:24 |
Mathieu Trudel-Lapierre |
grub2-signed (Ubuntu): status |
New |
Fix Released |
|
| 2016-08-03 20:56:27 |
Mathieu Trudel-Lapierre |
grub2-signed (Ubuntu Xenial): status |
New |
In Progress |
|
| 2016-08-03 20:56:28 |
Mathieu Trudel-Lapierre |
grub2-signed (Ubuntu): importance |
Undecided |
High |
|
| 2016-08-03 20:56:30 |
Mathieu Trudel-Lapierre |
grub2-signed (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2016-08-03 20:56:32 |
Mathieu Trudel-Lapierre |
grub2-signed (Ubuntu Xenial): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2016-08-11 22:46:21 |
Brian Murray |
grub2 (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-08-11 22:46:26 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-08-11 22:46:28 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2016-08-11 22:46:39 |
Brian Murray |
tags |
|
verification-needed |
|
| 2016-08-11 22:48:29 |
Brian Murray |
grub2-signed (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-08-12 21:58:28 |
Mike Pontillo |
bug task added |
|
maas |
|
| 2016-08-12 21:58:42 |
Mike Pontillo |
maas: status |
New |
Confirmed |
|
| 2016-08-12 21:58:48 |
Mike Pontillo |
maas: importance |
Undecided |
High |
|
| 2016-08-12 21:58:49 |
Mike Pontillo |
maas: milestone |
|
2.1.0 |
|
| 2016-08-12 21:58:57 |
Mike Pontillo |
maas: assignee |
|
LaMont Jones (lamont) |
|
| 2016-08-15 19:11:34 |
Simon Déziel |
bug |
|
|
added subscriber Simon Déziel |
| 2016-08-19 13:31:58 |
LaMont Jones |
attachment added |
|
dhcpd6 config file https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1229458/+attachment/4723999/+files/dhcpd6.conf |
|
| 2016-08-19 13:33:12 |
LaMont Jones |
attachment added |
|
screenshot of the failed attempt https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1229458/+attachment/4724000/+files/1229458-screenshot.jpg |
|
| 2016-08-19 13:33:39 |
LaMont Jones |
grub2 (Ubuntu): status |
Fix Released |
In Progress |
|
| 2016-09-08 14:32:15 |
Andres Rodriguez |
tags |
verification-needed |
maas-ipv6 verification-needed |
|
| 2016-09-15 17:49:31 |
Mathieu Trudel-Lapierre |
grub2 (Ubuntu): status |
In Progress |
Fix Released |
|
| 2016-09-26 13:55:34 |
Gavin Panella |
maas: status |
Confirmed |
Triaged |
|
| 2016-09-26 19:34:06 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Brian Murray |
| 2016-09-26 19:34:10 |
Ubuntu Foundations Team Bug Bot |
tags |
maas-ipv6 verification-needed |
maas-ipv6 verification-failed verification-needed |
|
| 2016-09-26 21:01:36 |
Steve Langasek |
tags |
maas-ipv6 verification-failed verification-needed |
maas-ipv6 verification-needed |
|
| 2016-10-06 15:19:33 |
Andres Rodriguez |
maas: status |
Triaged |
Fix Released |
|
| 2016-10-06 21:16:39 |
Mathieu Trudel-Lapierre |
description |
[Impact]
Trying to PXE boot (with UEFI) over IPv6 with grub. This is especially relevant for MAAS users in IPv6 setups.
[Test cases]
0) Setup PXE boot infrastructure (https://wiki.ubuntu.com/UEFI/SecureBoot-PXE-IPv6, also https://github.com/openSUSE/kiwi/wiki/Setup-PXE-boot-with-EFI-Using-GRUB2 contains relevant information)
1) Attempt to PXE boot (with UEFI) over IPv6 a system.
Testers can use grubnetx64.efi.signed from http://archive.ubuntu.com/ubuntu/dists/xenial-proposed/main/uefi/grub2-amd64/current/ once the package is available in proposed.
[Regression potential]
Possible regressions include any issues in routing IPv4 or IPv6 and/or retrieving files over PXE/tftp via grub. Ping is a good way to validate that routing is being done correctly, so is actually booting using the build grubnetx64.efi.
---
Testing using the pre-built grubnetx64.efi, I am not able to use the tftp client support within grub2 to load configs (/kernels/initrds) over the network. This works fine if using IPv4.
grubnetx64.efi is being loaded over the network (via shim no less), so the firmware's network stack is definitely up and working. But when grub tries to load grub.cfg via the default path, it fails with:
error: couldn't send network packet.
This message is repeated, approximately once every three seconds. It looks to be an infinite loop; at least, the message is repeated more than 100 times. But sometimes, when I've not been paying close attention to the boot, I get a grub shell instead. In that case, the grub shell shows:
grub> echo $root
tftp,0.5.0.24
grub> set
[...]
net_default_server=
net_efinet2_boot_file=8:23f::2]/bootx64.efi
net_efinet2_ip=0.0.0.0
net_efinet2_mac=02:3f:00:00:00:00
[...]
prefix=(tftp,0.5.0.24)/grub
pxe_default_server=
root=tftp,0.5.0.24
[...]
grub>
The actual server IP is 2001:1938:23f::2.
I've booted a locally-generated (self-signed) grubnetx64.efi with grub-bootstrap.cfg modified to call 'set' first, and I get identical output for all of the network-related variables. |
[Impact]
Trying to PXE boot (with UEFI) over IPv6 with grub. This is especially relevant for MAAS users in IPv6 setups.
[Test cases]
[IPv6 PXE boot]
0) Setup PXE boot infrastructure (https://wiki.ubuntu.com/UEFI/SecureBoot-PXE-IPv6, also https://github.com/openSUSE/kiwi/wiki/Setup-PXE-boot-with-EFI-Using-GRUB2 contains relevant information)
1) Attempt to PXE boot (with UEFI) over IPv6 a system.
[IPv4 PXE boot]
0) Setup PXE boot infrastructure;
Required DHCP config:
- filename should specify the path to the efi binary to use to boot, or to pxelinux in a non-EFI case.
- next-server should be set to the TFTP server.
1) Attempt to PXE boot (with and without UEFI) with IPv4.
[IPv4 PXE boot with HTTPClient]
0) Setup PXE boot infrastructure;
Required DHCP config:
- set vencor class to HTTPClient.
- configure filename to be the url to the pxelinux (non-UEFI) or EFI binary (UEFI)
- next-server should be set to the TFTP server.
1) Attempt to PXE boot (with and without UEFI) with IPv4.
[MaaS deployment in IPv4 network]
1) deploy a system using MaaS in an IPv4-only network.
[MaaS deployment in IPv6 network]
1) deploy a system using MaaS in an IPv6-only network.
[MaaS deployment in a mixed network]
1) deploy a system using MaaS on a network with both IPv4 and IPv6.
Testers can use grubnetx64.efi.signed from http://archive.ubuntu.com/ubuntu/dists/xenial-proposed/main/uefi/grub2-amd64/current/ once the package is available in proposed.
[Regression potential]
Possible regressions include any issues in routing IPv4 or IPv6 and/or retrieving files over PXE/tftp via grub. Ping is a good way to validate that routing is being done correctly, so is actually booting using the build grubnetx64.efi.
---
Testing using the pre-built grubnetx64.efi, I am not able to use the tftp client support within grub2 to load configs (/kernels/initrds) over the network. This works fine if using IPv4.
grubnetx64.efi is being loaded over the network (via shim no less), so the firmware's network stack is definitely up and working. But when grub tries to load grub.cfg via the default path, it fails with:
error: couldn't send network packet.
This message is repeated, approximately once every three seconds. It looks to be an infinite loop; at least, the message is repeated more than 100 times. But sometimes, when I've not been paying close attention to the boot, I get a grub shell instead. In that case, the grub shell shows:
grub> echo $root
tftp,0.5.0.24
grub> set
[...]
net_default_server=
net_efinet2_boot_file=8:23f::2]/bootx64.efi
net_efinet2_ip=0.0.0.0
net_efinet2_mac=02:3f:00:00:00:00
[...]
prefix=(tftp,0.5.0.24)/grub
pxe_default_server=
root=tftp,0.5.0.24
[...]
grub>
The actual server IP is 2001:1938:23f::2.
I've booted a locally-generated (self-signed) grubnetx64.efi with grub-bootstrap.cfg modified to call 'set' first, and I get identical output for all of the network-related variables. |
|
| 2016-11-16 00:10:15 |
LaMont Jones |
tags |
maas-ipv6 verification-needed |
maas-ipv6 verification-done |
|
| 2016-12-20 20:39:49 |
Steve Langasek |
tags |
maas-ipv6 verification-done |
maas-ipv6 |
|
| 2016-12-20 20:39:51 |
Steve Langasek |
tags |
maas-ipv6 |
maas-ipv6 verification-needed |
|
| 2017-01-03 18:52:29 |
LaMont Jones |
tags |
maas-ipv6 verification-needed |
maas-ipv6 verification-done |
|
| 2017-01-03 22:28:46 |
Launchpad Janitor |
grub2 (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-01-03 22:28:57 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-01-03 22:29:25 |
Launchpad Janitor |
grub2-signed (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
