Spurious conffile prompts for /etc/default/grub
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Debian) |
Fix Released
|
Unknown
|
|||
grub2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned | ||
grub2-signed (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
All users of Ubuntu, especially on updates of the grub packages. (Grub is used nearly everywhere to boot)
[Test case]
== Upgrade prompting ==
0) Install Ubuntu
1) Modify /usr/share/
2) Run 'sudo apt install --reinstall grub-pc ((or grub-efi-amd64))
Verify that the user IS prompted to approve grub.cfg changes due to changes in the template coming from the process.
== User-specified changes ==
0) Install Ubuntu
1) Modify /etc/default/
2) Update grub to the new package
Verify that the user is not prompted to approve grub.cfg changes unless the grub2 package unless the grub packages have changed the contents of the default grub.cfg.
== Post-deployment upgrades on MAAS-controlled system ==
0) Deploy a system using MAAS
1) Update grub to the new package
Verify that the user is not prompted to approve grub.cfg changes unless the grub2 package unless the grub packages have changed the contents of the default grub.cfg.
[Regression potential]
Pay attention to prompting behavior on grub updates as well as any failure to update the grub* packages. Prompting should be limited to the cases where the grub2 source package has changed the contents for the default provided grub.cfg; and on MAAS-controlled systems, the local modifications have changed in some way from the original copy of grub2 installed on the system.
---
Binary package hint: grub-pc
This concerns grub-pc 1.98-1ubuntu5 in Lucid beta1 (upgrading from 1.98-1ubuntu4).
I have a locally modified /etc/default/grub file. When I upgraded to this version of grub-pc, I got the "A new version of configuration file /etc/default/grub is available, but the version installed currently has been locally modified. What do you want to do about modified configuration file grub?" question.
The problem is, when I look at the diff, it just shows the differences between my file, and the way it was originally. In other words, the upgraded package does not include any updates to this file; its "pristine" copy of /etc/default/grub is the same as the previous version's. So I shouldn't even be getting a conffile prompt in the first place---as far as the administrator is concerned, nothing has changed.
Changed in grub2 (Ubuntu): | |
status: | New → Confirmed |
Changed in grub2 (Debian): | |
status: | Unknown → New |
Changed in grub2 (Debian): | |
status: | New → Fix Committed |
Changed in grub2 (Debian): | |
status: | Fix Committed → Fix Released |
tags: | added: id-5c5c539ad3b453093101b6b0 |
description: | updated |
description: | updated |
tags: | added: verification-done |
Scott, thank you for providing the script, and the analysis that led to it. I've run into this issue numerous times but have not been able to suss out exactly what leads to it such that it can be reproduced.
I've linked a relevant Debian bug, which appears to address the same issue, and was filed more recently.