grub-pc reinstallation throws a prompt asking the device it should install on for Noble
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-images |
Fix Released
|
Undecided
|
Utkarsh Gupta | ||
| grub2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| ubuntu-release-upgrader (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
grub-pc requires knowing what device to grub-install on, but when cloud images are generated, the device on the deployment target is never known. And so when the package is reinstalled (for example, when unminimizing the minimized image), the user gets that prompt, asking where to install the grub, when this should happen non-interactively, for example, by determining where the grub was first installed.
Interestingly, this issue always existed, however it was masked by the following timeline:
In July 2020, it was discovered that certain scenarios can cause grub-pc installation to fail, and an emergency SRU https:/
Before the commit https:/
In Dec 2021, grub2 2.06-2ubuntu1 was uploaded containing the previously mentioned commit. But as a result of the above emergency SRU, that upload managed to silently change the status quo without it ever being noticed.
In December 2023, the grub-pc installation workaround was finally removed in https:/
The plausible solution is to develop something to set the grub-pc/
Related branches
- Mate Kukri: Approve
- Utkarsh Gupta: Approve
-
Diff: 29 lines (+10/-0)2 files modifieddebian/changelog (+7/-0)
live-build/ubuntu-cpc/hooks.d/base/disk-image-uefi.binary (+3/-0)
| description: | updated |
| Mate Kukri (mkukri) wrote | #1 |
| Mate Kukri (mkukri) wrote | #2 |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in grub2 (Ubuntu): | |
| status: | New → Fix Released |
| Changed in cloud-images: | |
| status: | New → Fix Released |
| assignee: | nobody → Utkarsh Gupta (utkarsh) |
First we are going to change grub to not hard-error when `grub-pc/
Second, since we know the image layout on cloud images, we can use `grub-probe` to determine the install device based on the filesystem containing the `/boot` directory.
We are introducing the `grub-{
This can then be set in cloud images at build time, and reinstallation should just work this way without having to introduce a new service.