Unattended "apt-get dist-upgrade -qq --force-yes" on 14.04 fails on grub configuration.

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1323772/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

Is this when upgrading to 14.04? If so from what release? Or is this when upgrading from 14.04 to 14.10?

No when using dist-upgrade as stated. The kernel was upgraded from 3.13.0-24 to 3.13.0-27. The current AMI, at given URL, seems to have been upgraded to 3.13.0-27 so the case is not reproducible from that source. Yet it might happen with later upgrades.

Any news on this Brian? This should be reproducable by using AMIs with kernel 3.13.0-24.

This bug breaks any automated tooling in building AMsI using ubuntu.

to reproduce:

Launch in us-west-1 ami-c6bdba83 (found via https://cloud-images.ubuntu.com/locator/ec2/)

This ami is a:

us-west-1 trusty 14.04 LTS amd64 hvm:ebs-ssd 20140607.1 ami-c6bdba83 hvm

to reproduce

sudo apt-get update
sudo apt-get -y upgrade
sudo reboot # just because, likely not necessary

sudo apt-get -y dist-upgrade (and various other -force-yes)

Now complains about /boot/grub/menu.lst being modified and in conflict with update.

the fix is what peter.waller suggested in https://bugs.launchpad.net/cloud-init/+bug/1309079?comments=all

before fist-upgrade do the following

sudo rm /boot/grub/menu.lst
sudo update-grub-legacy-ec2 -y
sudo apt-get -y dist-upgrade

please advise.

thanks!

nickg

Status changed to 'Confirmed' because the bug affects multiple users.

Why is there no response to this bug? You keep pushing up releases with this bug for no good reason!

Confirmed in the "eu 14.04 ebs ami-cb4986bc" version at https://cloud-images.ubuntu.com/locator/ec2/

Related bug marked as fixed: https://bugs.launchpad.net/ubuntu/+bug/1009294

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

Note that the bug https://bugs.launchpad.net/cloud-init/+bug/1309079 mentions that the work-around is not good enough. Will test myself today.

The work-around in https://bugs.launchpad.net/cloud-init/+bug/1309079/comments/5 did work as expected:

"sudo rm /boot/grub/menu.lst
sudo update-grub-legacy-ec2 -y
sudo apt-get dist-upgrade -qq --force-yes"

However, as I understand, the prompt will still appear when doing later upgrades.

I have filed separate bug 1485685 with a detailed investigation that perhaps covers this issue, but I deliberately didn't take over this bug in case it is different. I'll mark this as a duplicate for now; if when the other bug is fixed your issue still exists then we can always unduplicate.

(note that this isn't a bug in apt whichever way, so that's probably why this bug wasn't seen by relevant developers)

That makes no sense since the workaround in this thread is useful for those searching for a solution to the problem (this year) and your description appears to be the duplicate since it was filed later :-)

Secondly, this bug indicates that this is an bug with ties to older bugs, which can perhaps be of use. I.e., why is the bug not addressed properly, which is another issue to resolve. 11 people (at least) are affected as well which can give input instead of six.

I have deployed the workaround during several Ubuntu releases. It still works!

I've linked to this bug from my bug to make it clear.

> and your description appears to be the duplicate since it was filed later

Yes, but I think my root cause investigation is more useful to be the lead summary to actually get this fixed, which is why I did it this way round and explained what I did. Launchpad ties the bugs together as long as they are linked (including number of users affected). I'm just arranging the bugs this way to maximise the help to developers to get it fixed.