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

Steve Langasek steve.langasek at canonical.com
Wed Jun 6 05:55:38 UTC 2012


I believe this can be reproduced by:

 - installing grub
 - changing one or more of the settings in /etc/default/grub that are managed by debconf (GRUB_CMDLINE_LINUX, GRUB_CMDLINE_LINUX_DEFAULT, GRUB_TIMEOUT, GRUB_HIDDEN_TIMEOUT), and *also* changing one or more line in /etc/default/grub that is *not* managed by debconf
 - upgrading grub

I haven't seen the /etc/default/grub from the cloud image yet.  Can
someone attach a copy of the file for comparison?

And as to upgrading without a prompt, the correct workaround would be to
set DEBIAN_FRONTEND=noninteractive in the environment, to suppress all
debconf prompting.

-- 
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:
  In Progress
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




More information about the foundations-bugs mailing list