config-grub does not run
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Lucid |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: cloud-init
In testing bug 671103, I realised that the 'config-grub' code that was added is not actually invoked on boot. As a result, the changes will not seed grub2 correctly.
What should happen on first boot is that 'h_config_grub' in 'CloudConfig.py' should run and 'grub-pc/
Unfortunately, the fix added doesn't get that code invoked, and as a result, these values are not seeded.
What we see is:
$ debconf-
grub-pc grub-pc/
grub-pc grub-pc/
grub-pc grub-pc/
grub-pc grub-pc/
What we *should* see on EC2 is:
$ debconf-
grub-pc grub-pc/
grub-pc grub-pc/
grub-pc grub-pc/
grub-pc grub-pc/
Without those variables set, the user will be prompted on grub update.
===== SRU Information =====
* impact of the bug: this bug in cloud-init does not deliver a fix for bug 683379 that I hoped it would. The result is that on upgrade of grub-pc, the user is prompted to verify they do not need to install grub even if they have DEBIAN_
* how the bug has been addressed: In maverick, the same code runs in a different way. When I pulled the change back to lucid, i didn't get the code invoked.
* minimal patch: The changes are available in my branch at [1], the diff from that which entered -proposed under bug 671103 can be seen from tip of the branch to revision 19. [2].
* instructions on how to reproduce the bug:
* boot instance on ec2, upgrade grub-pc. The user will be prompted as to if they want to continue without installing grub even though grub-pc is of no use on EC2.
There is *no* potential for regression on running systems, only on systems where a user chooses to install grub-legacy-ec2 *and* modifies their instance to use pv-grub.
--
[1] https:/
[2] http://
=====
description: | updated |
tags: |
added: verification-done removed: verification-needed |
This is not truely a regression, but rather a fix (to bug 683379) that won't get put in.