MAAS is dropped in grub menu when booting in UEFI mode, and Secure Boot not working
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
New
|
Undecided
|
Unassigned |
Bug Description
We try to certify our products, we are able to do everything easily in Legacy mode.
In UEFI mode, we have to modify some files.
When we boot the node, we are not able to enlist it with a 1Gb interface, we are only able to do the process with a 10Gb interface.
The node never appear into the MAAS console, the process cannot go further the grub. it failed after Fetching netboot image
When we are in grub, we are not able to type command, the result is couldn't send network packet, but our product receive a valid address.
We also try by removing all partitions from the disk and its doesn't work neither.
We also try to disable all interfaces expect one and the same problem occur.
into the BIOS all UEFI options are enable and working with an another pxe boot in UEFI (Not a MAAS server)
Our drivers :
1Gb interface : i210 & i350
10Gb interface : X552 & X710
On MAAS:
cd /var/lib/
sudo wget http://
sudo mv grubx64.efi grubx64.orig
sudo mv grubnetx64.
wget https:/
sudo dpkg -i grub-efi-
sudo apt-get install grub-efi-
On our SUT we have to do these lines to enable the Secure Boot:
sudo apt-get install shim-signed
sudo update-grub
lsblk
### X = where /boot/efi partition is installed.
sudo grub-install --target=x86_64-efi --efi-directory
How to reproduce,
Install Ubuntu Vanilla
Follow the MANIAC guide to install/configure the MAAS server.
Put a client in UEFI mode and boot from pxe.
Our versions :
Linux maas-cert 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 16.04.3 LTS
MAAS Version
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 2.2.2-6099-
ii maas-cert-server 0.2.30-
ii maas-cli 2.2.2-6099-
un maas-cluster-
ii maas-common 2.2.2-6099-
ii maas-dhcp 2.2.2-6099-
ii maas-dns 2.2.2-6099-
ii maas-proxy 2.2.2-6099-
ii maas-rack-
ii maas-region-api 2.2.2-6099-
ii maas-region-
un maas-region-
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-
ii python3-django-maas 2.2.2-6099-
ii python3-maas-client 2.2.2-6099-
ii python3-
I'm not 100% positive, but this sounds like a duplicate of bug #1437024.