Users are prompted on upgrade of cloud images
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
High
|
Unassigned |
Bug Description
Steps to reproduce (use case):
1. Fire up a Trusty cloud image.
2. Run: sudo apt-get update && sudo apt-get -y dist-upgrade
Steps to reproduce (developer):
1. Fire up an older image that does not contain the newest grub2 SRU. Example: http://
2. Run: sudo apt-get update && sudo apt-get -y dist-upgrade
Expected results: completes without prompts.
Actual results: prompts the user for input to resolve a "manually" changed /boot/grub/
User impact: this messes up automation; it is a common use of cloud images for users to automate their server deployments which generally involves running a dist-upgrade and then bootstrapping some kind of configuration management system.
This means that we cannot SRU grub2 without breaking some set of users in a fairly common use case of cloud images until users start using newer images with the new SRU'd grub2 rolled in.
Workaround: users can use something like: apt-get update && UCF_FORCE_CONFOLD=1 apt-get -y dist-upgrade. Note that to avoid prompts in various other cases users should also set DEBIAN_
Investigation:
I noticed that running "sudo update-
I suspect that menu.lst is being changed without ucf being updated in the image build process. Line 421 "_xchroot "${rootd}" /usr/bin/ucfr --purge grub /var/run/
tags: | added: bot-stop-nagging |
Changed in cloud-init (Ubuntu): | |
importance: | Undecided → Medium |
assignee: | Robert C Jennings (rcj) → nobody |
tags: | removed: bot-stop-nagging |
Changed in cloud-images: | |
status: | New → Confirmed |
importance: | Undecided → High |
no longer affects: | cloud-init (Ubuntu) |
Status changed to 'Confirmed' because the bug affects multiple users.