Failure to PXE-boot from secondary NIC
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Wishlist
|
Unassigned | ||
grub2 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Triaged
|
High
|
Mathieu Trudel-Lapierre | ||
Xenial |
Triaged
|
High
|
Mathieu Trudel-Lapierre |
Bug Description
On a Lenovo x3550 M5 with the standard 4-port 1Gbps NICs and a secondary (plug-in) 2-port 10Gbps NIC, an attempt to PXE-boot from the secondary NIC in UEFI mode causes a boot failure with a "grub>" prompt on the display.
This server arrived for certification with both NICs enabled. I suspect, but am not positive, that which NIC is chosen for booting is semi-random, although it favors the secondary NIC. The system PXE-boots fine from the built-in ports (generally the first one, eth0), and when booting from eth0 is forced via the UEFI boot menu, enlistment, commissioning, deployment, and post-deployment booting all work fine.
When the system PXE-boots from the secondary NIC, though, the normal UEFI PXE-boot messages appear on the screen, followed by the aforementioned "grub>" prompt. This obviously prevents normal operation of the server with MAAS. It appears from the logs (attached) that when using the failed NIC, the MAAS server doesn't receive follow-on requests from GRUB.
As a workaround, the secondary NICs can be configured to not support PXE-booting in the firmware setup utility; this enables normal deployment via MAAS.
MAAS version information:
$ dpkg -l '*maas*'|cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 1.7.2+bzr3355-
ii maas-cli 1.7.2+bzr3355-
ii maas-cluster-
ii maas-common 1.7.2+bzr3355-
ii maas-dhcp 1.7.2+bzr3355-
ii maas-dns 1.7.2+bzr3355-
ii maas-proxy 1.7.2+bzr3355-
ii maas-region-
ii maas-region-
ii python-django-maas 1.7.2+bzr3355-
ii python-maas-client 1.7.2+bzr3355-
ii python-
tags: | added: uefi |
Changed in maas: | |
milestone: | none → next |
summary: |
- Failure to PXE-boot from secondary NIC + Unable to UEFI boot machine over IPv6 |
Changed in maas: | |
milestone: | next → 1.8.0 |
importance: | High → Critical |
Changed in maas: | |
milestone: | 1.8.0 → next |
Changed in maas: | |
importance: | Critical → Wishlist |
This seems to be very similar to bug 1437353, targeting to grub2 as well.