grub-reboot changes boot default permanently on Lucid LTS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Fix Released
|
Undecided
|
dann frazier | ||
Bionic |
Fix Released
|
Undecided
|
dann frazier | ||
grub2-signed (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
The grub-reboot manpage says it will "Set the default boot menu entry for GRUB, for the next boot only." But, that's a promise it cannot keep when GRUB cannot write to the environment block, such as when it is stored on Linux software RAID (md) or LVM devices. An administrator of such a system may expect grub-reboot to work as documented, only to find that their change is now permanent, requiring manual recovery. Users without console access may rely on grub-reboot to provide a mechanism for testing a possible-broken boot entry. If that entry causes the system to fail to boot, they may find their system unrecoverable.
[Test Case]
Run grub-reboot on an impacted system and check for a warning and instructions on manually restoring the default. Also, check for a warning in the grub-reboot manpage.
[Regression Risk]
This is a documentation change only. The documentation is emitted by (trivial) code, so a bug in that code could lead to unintentional functional changes.
Changed in grub2 (Ubuntu): | |
status: | Confirmed → In Progress |
Changed in grub2 (Ubuntu Bionic): | |
status: | New → In Progress |
description: | updated |
Changed in grub2 (Ubuntu Bionic): | |
assignee: | nobody → dann frazier (dannf) |
Changed in grub2 (Ubuntu): | |
assignee: | nobody → dann frazier (dannf) |
It appears that this bug may not actually be related to bug #497326 as per the recent update in that thread. Perhaps this has more to do with the disk configuration that's being used?