This bug was fixed in the package cloud-init - 0.5.10-0ubuntu1.5
---
cloud-init (0.5.10-0ubuntu1.5) lucid-proposed; urgency=low
* make grub-config code run on instance first boot so user is not
prompted on grub upgrade (LP: #683890, LP: #683379)
cloud-init (0.5.10-0ubuntu1.4)
** Tags added: verification-done
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in ubuntu.
https://bugs.launchpad.net/bugs/683890
Title:
config-grub does not run
--
Accepted cloud-init into lucid-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: cloud-init (Ubuntu
I just verified this on
ap-southeast-1 ami-ce601e9c canonical ubuntu-lucid-daily-i386-server-20101203.1
That build was built with -proposed enabled.
$ dpkg-query --show cloud-init grub-legacy-ec2
cloud-init 0.5.10-0ubuntu1.5
grub-legacy-ec2 0.5.10-0ubuntu1.5
$ debconf-get-selections
This is not truely a regression, but rather a fix (to bug 683379) that
won't get put in.
** Also affects: cloud-init (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Low
** Changed in: cloud-init (Ubuntu)
Status: New
** Branch linked: lp:~smoser/ubuntu/lucid/cloud-init/lucid-kernel-
upgrades
--
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
** 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'
