Installation failure on UEFI systems using older images with automatic download of updates enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2-signed (Ubuntu) |
Fix Released
|
Critical
|
Łukasz Zemczak | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Critical
|
Łukasz Zemczak | ||
Cosmic |
Fix Released
|
Critical
|
Łukasz Zemczak |
Bug Description
[Impact]
Recent grub2-signed dependency chain changes required some changes to be made to the installer parts to make sure the end system is bootable. However, older isos (like, release images for bionic) do not have these installer changes, so users using those with automatic download of updates enabled on UEFI systems will end up with a broken system.
[Test Case]
Checking if the bug has been fixed:
* Download an older iso (for bionic, let it be the 18.04 release image)
* Prepare an UEFI-based VM
* Install Ubuntu with automatic download of updates enabled
* Reboot and make sure the system is bootable
Checking if no regressions have been introduced for the installer:
* Download the latest daily server iso
* Prepare an UEFI-based VM
* Install Ubuntu
* Reboot and make sure the system is bootable
[Regression Potential]
There should be no real regression potential here as we are basically adding dependencies that should otherwise be installed when using a newer image. All potential regressions would be made visible during the installation tests from the test case.
[Original Description]
Regression caused by https:/
Steps to reproduce
1) Install ubuntu-
2) Reboot the VM
3) See GRUB shell instead of GDM
The system can be rescued by running
configfile (hd0,gpt2)
at the GRUB shell
Installing grub-efi-amd64 in the rescued system then makes it bootable.
Previously grub-efi-
Additionally, the removal of this dependency has resulted in a very sparse /etc/default/grub after installation.
I've attached a simple script for installation with QEMU and OVMF.
I suspect that installs are broken on actual hardware with SecureBoot disabled, but I'm not able to test that right now.
description: | updated |
tags: |
added: verification-done verification-done-bionic removed: verification-needed verification-needed-bionic |
At a glance, it appears to me that grub-efi- amd64-signed is missing a dependency on grub-efi-amd64 | grub-pc, which I believe was discussed as a requirement but seems not to have been fixed in the version that was SRUed.