To clarify, the fixes tested only fix the cloud-init piece. Since the cloud-init module in question only runs at first boot. So while the patch does address the problem, it only fixes it for future instances. Existing instances that upgrade grub will be broken. Meaning that if a ABI changes takes place in 14.04, this bug will also affect 14.04.
We need to come up a fix for existing instances as well. ** Description changed: + Cloud-init, as part of the first boot configures grub-pc to set the + device that grub should install to. However, in the case of HVM + instances, /dev/xvda and /dev/xvda1 are not considered (only sda, sda1, + vda and vda1). Since AWS HVM instances and Xen use /dev/xvdX devices, + this means that any Grub update with an ABI change will break the + instances, rendering them unable to boot. + + + ----ORIGINAL report---- + It looks like a recent update to grub or the kernel on 12.04 is breaking - unattended installs on EC2 for HVM instances. + unattended installs on EC2 for HVM instances. You can reproduce the problem by doing the following: region: us-east-1 virtualization type: HVM (e.g. r3.xlarge) AMI ID: ami-7a916212 dpkg --configure –a apt-get update apt-get install -y ruby ruby-dev libicu-dev libssl-dev libxslt-dev libxml2-dev monit apt-get dist-upgrade –y -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1336855 Title: [SRU] non-interactive grub updates for 12.04 break on AWS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1336855/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
