yahoo-eng-team team mailing list archive

[Peter Waller <p@xxxxxxxxxxx>]

Public bug reported:

This bug has been observed with at least EC2 AMI: ami-ec50a19b
"ubuntu/images/ebs/ubuntu-saucy-13.10-amd64-server-20140212", and other
Ubuntu saucy AMIs.

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-grub-legacy-ec2
7. observe file not updated

This is especially insidious because it claims the file is updated, with
output like this:

> Found kernel: /boot/vmlinuz-3.11.0-19-generic
> Found kernel: /boot/vmlinuz-3.11.0-18-generic
> Found kernel: /boot/vmlinuz-3.11.0-17-generic
> Found kernel: /boot/vmlinuz-3.11.0-15-generic
> Found kernel: /boot/vmlinuz-3.11.0-14-generic
> Found kernel: /boot/vmlinuz-3.11.0-12-generic
> Found kernel: /boot/memtest86+.bin
> 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_CONFFNEW=1 and DEBIAN_PRIORITY=low and:

> # debconf-get-selections | grep grub-l
> grub-legacy-ec2    grub/update_grub_changeprompt_threeway    select    install_new

don't have any useful effect.

I've emailed Ben Howard who confirmed he could reproduce this bug.

** Affects: cloud-init
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1309079

Title:
  Running update-grub-legacy-ec2 doesn't cause /boot/grub/menu.lst

Status in Init scripts for use on cloud images:
  New

Bug description:
  This bug has been observed with at least EC2 AMI: ami-ec50a19b
  "ubuntu/images/ebs/ubuntu-saucy-13.10-amd64-server-20140212", and
  other Ubuntu saucy AMIs.

  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-grub-legacy-ec2
  7. observe file not updated

  This is especially insidious because it claims the file is updated,
  with output like this:

  > Found kernel: /boot/vmlinuz-3.11.0-19-generic
  > Found kernel: /boot/vmlinuz-3.11.0-18-generic
  > Found kernel: /boot/vmlinuz-3.11.0-17-generic
  > Found kernel: /boot/vmlinuz-3.11.0-15-generic
  > Found kernel: /boot/vmlinuz-3.11.0-14-generic
  > Found kernel: /boot/vmlinuz-3.11.0-12-generic
  > Found kernel: /boot/memtest86+.bin
  > 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_CONFFNEW=1 and DEBIAN_PRIORITY=low and:

  > # debconf-get-selections | grep grub-l
  > grub-legacy-ec2    grub/update_grub_changeprompt_threeway    select    install_new

  don't have any useful effect.

  I've emailed Ben Howard who confirmed he could reproduce this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1309079/+subscriptions