** Description changed: 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/install_devices' and 'grub- pc/install_devices_empty' should get seeded. Unfortunately, the fix added doesn't get that code invoked, and as a result, these values are not seeded. What we see is: $ debconf-get-selections 2>/dev/null | grep grub-pc/install grub-pc grub-pc/install_devices_failed boolean false grub-pc grub-pc/install_devices multiselect grub-pc grub-pc/install_devices_disks_changed multiselect grub-pc grub-pc/install_devices_empty boolean false What we *should* see on EC2 is: $ debconf-get-selections 2>/dev/null | grep grub-pc/install grub-pc grub-pc/install_devices_failed boolean false grub-pc grub-pc/install_devices_disks_changed multiselect grub-pc grub-pc/install_devices_empty boolean true - grub-pc grub-pc/install_devices string + grub-pc grub-pc/install_devices string 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_FRONTEND=noninteractive. + * 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://code.launchpad.net/~smoser/ubuntu/lucid/cloud-init/lucid-kernel-upgrades + [2] http://bazaar.launchpad.net/~smoser/ubuntu/lucid/cloud-init/lucid-kernel-upgrades/revision/20?remember=19&compare_revid=19 + =====
-- config-grub does not run https://bugs.launchpad.net/bugs/683890 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
