Running update-grub-legacy-ec2 doesn't update kernel list in /boot/grub/menu.lst
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
Undecided
|
Unassigned | ||
grub-legacy-ec2 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
This bug has been observed with at least EC2 AMI: ami-ec50a19b "ubuntu/
Steps to reproduce:
1. sudo apt-get update
2. sudo apt-get dist-upgrade
3. Get prompted for one thing, whether to install the maintainer's version of /boot/grub/menu.lst (choose to use the maintainer's file)
4. observe updated file
5. modify the file to remove the new entries
6. run update-
7. observe file not updated
This is especially insidious because it claims the file is updated, with output like this:
> Found kernel: /boot/vmlinuz-
> Found kernel: /boot/vmlinuz-
> Found kernel: /boot/vmlinuz-
> Found kernel: /boot/vmlinuz-
> Found kernel: /boot/vmlinuz-
> Found kernel: /boot/vmlinuz-
> Found kernel: /boot/memtest86
> Updating /boot/grub/menu.lst ... done
And in fact, /boot/grub/menu.lst has its modified time updated to now, but it doesn't actually change the contents of the file.
This is extremely confusing.
I note that UCF_FORCE_
> # debconf-
> grub-legacy-ec2 grub/update_
don't have any useful effect.
I've emailed Ben Howard who confirmed he could reproduce this bug.
summary: |
- Running update-grub-legacy-ec2 doesn't cause /boot/grub/menu.lst + Running update-grub-legacy-ec2 doesn't update kernel list in + /boot/grub/menu.lst |
I've confirmed that this happens on non-EC2 systems. I was able to replicate this on Canonistack (OpenStack) but not on EC2.