| 2010-12-01 21:47:06 |
Scott Moser |
bug |
|
|
added bug |
| 2010-12-01 21:47:38 |
Scott Moser |
tags |
|
ec2-images regression-proposed uec-images |
|
| 2010-12-01 21:48:36 |
Scott Moser |
nominated for series |
|
Ubuntu Lucid |
|
| 2010-12-01 21:48:36 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Lucid) |
|
| 2010-12-01 21:48:50 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
Low |
|
| 2010-12-01 21:48:50 |
Scott Moser |
cloud-init (Ubuntu): status |
New |
Fix Released |
|
| 2010-12-01 21:48:59 |
Scott Moser |
cloud-init (Ubuntu Lucid): status |
New |
Triaged |
|
| 2010-12-01 21:49:04 |
Scott Moser |
cloud-init (Ubuntu Lucid): importance |
Undecided |
High |
|
| 2010-12-01 22:09:34 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/lucid/cloud-init/lucid-kernel-upgrades |
|
| 2010-12-01 22:11:51 |
Scott Moser |
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/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
Without those variables set, the user will be prompted on grub update. |
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
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
=====
|
|
| 2010-12-03 15:49:49 |
Martin Pitt |
cloud-init (Ubuntu Lucid): status |
Triaged |
Fix Committed |
|
| 2010-12-03 15:49:52 |
Martin Pitt |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2010-12-03 15:49:55 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2010-12-03 15:49:58 |
Martin Pitt |
tags |
ec2-images regression-proposed uec-images |
ec2-images regression-proposed uec-images verification-needed |
|
| 2010-12-06 18:33:03 |
Scott Moser |
tags |
ec2-images regression-proposed uec-images verification-needed |
ec2-images regression-proposed uec-images verification-done |
|
| 2010-12-13 19:37:45 |
Launchpad Janitor |
cloud-init (Ubuntu Lucid): status |
Fix Committed |
Fix Released |
|
| 2011-01-18 19:11:37 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/lucid-updates/cloud-init |
|
