UEFI-mode Bionic deployments failing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned | ||
curtin |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Ubuntu 18.04 deployments in UEFI mode have recently begun failing at GRUB installation. The attempt produces normal installation output up until the GRUB installation, when this appears:
Setting up shim (13-0ubuntu2) ...
Setting up libefivar1:amd64 (34-1) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Setting up sbsigntool (0.6-3.2ubuntu2) ...
Setting up libefiboot1:amd64 (34-1) ...
Processing triggers for man-db (2.8.3-2) ...
Setting up mokutil (0.3.0-0ubuntu5) ...
Setting up secureboot-db (1.1) ...
Can't access efivars filesystem at /sys/firmware/
Setting up efibootmgr (15-1) ...
Setting up grub-efi-amd64-bin (2.02-2ubuntu8) ...
Setting up grub-efi-amd64 (2.02-2ubuntu8) ...
Replacing config file /etc/default/grub with new version
Setting up shim-signed (1.34.6+
Setting up grub-efi-
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Unexpected error while running command.
Command: ['sh', '-c', 'exec "$0" "$@" 2>&1', 'install-grub', '--uefi', '--update-nvram', '/tmp/tmpuek345
Exit code: 1
Reason: -
Stdout: + echo before grub-install efiboot settings
before grub-install efiboot settings
+ efibootmgr
Timeout: 1 seconds
BootOrder: 0002,0003,0001
Boot0001* UEFI C400-MTFDDAT064MAM MSA1727018J
Boot0002* UEFI PXEv4 (MAC:ECA86BFF33AD)
Boot0003* UEFI PXEv6 (MAC:ECA86BFF33AD)
+ dpkg-reconfigure grub-efi-amd64
Replacing config file /etc/default/grub with new version
Processing triggers for shim-signed (1.34.6+
No MOK found.
dpkg: error processing package shim-signed (--configure):
installed shim-signed package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
failed to install grub!
Stderr: ''
curtin: Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'curthooks']
Exit code: 3
Reason: -
The first sign of trouble that I see is the complaint about being unable to access /sys/firmware/
I've reproduced this problem occurs on about half a dozen nodes on three MAAS servers. The problem does NOT occur when deploying Ubuntu 16.04, but DOES occur when deploying the latest pre-release 18.04. I'm attaching a tarball of /var/log/maas from one of the MAAS servers. The test system on that server is brennan.
$ dpkg -l '*maas*'|cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 2.3.2-6485-
ii maas-cert-server 0.2.36-
ii maas-cli 2.3.2-6485-
un maas-cluster-
ii maas-common 2.3.2-6485-
ii maas-dhcp 2.3.2-6485-
ii maas-dns 2.3.2-6485-
ii maas-proxy 2.3.2-6485-
ii maas-rack-
ii maas-region-api 2.3.2-6485-
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.3.2-6485-
ii python3-maas-client 2.3.2-6485-
ii python3-
Can you please attach the curtin config?
maas <user> machine get-curtin-config <system_id>