[Bug 1009294] Re: Grub update breaks automated dist-upgrade scripts on AMI images

[Dave Walker]

As outlined by Steve in comment #7, the fix for this is in the cloud image building tools to add:
  DEBIAN_FRONTEND=noninteractive dpkg-reconfigure grub-pc

A suitable validation of this is to run a instance pre-grub2 update, run
this command, then upgrade.  If it doesn't prompt, then we should have a
suitable resolution.

However, this resolution will not resolve currently deployed AMI's
before this is resolved, only latest builds.  ~smoser is assigned to
land this fix in the build tools for newer AMI's.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1009294

Title:
  Grub update breaks automated dist-upgrade scripts on AMI images

Status in “grub2” package in Ubuntu:
  Triaged
Status in “grub2” source package in Precise:
  In Progress

Bug description:
  The update committed here:
  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/978464  appears
  to have exposed a bug in either grub or apt that is breaking scripts
  based on the Amazon images from cloud.ubuntu.com.

  See http://askubuntu.com/questions/146921/how-do-i-apt-get-y-dist-
  upgrade-without-a-grub-config-prompt

  
  Specifically, dpkg is giving the upgraded config file prompt upon configuring grub-pc ("A new version of configuration file /etc/default/grub is available, but the version installed currently has been locally modified.")

  However, the following does not work:
  sudo apt-get update
  sudo apt-get -y -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" dist-upgrade

  Furthermore, dpkg -S /etc/default/grub  doesn't appear to show this
  file as being owned by any package prior to upgrade.  I'm not sure how
  this file is generated (or how dpkg determines who owns it), but it's
  currently breaking scripts and I can't figure out a way to work around
  it short of deleting the file prior to the upgrade (which probably
  isn't safe).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1009294/+subscriptions