** No longer affects: ubuntu-on-ec2
--
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/665235
Title:
grub-legacy-ec2: attaching a volume to maverick instance may boot off
it
To ma
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Won't Fix
--
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/665235
Title:
grub-legacy-ec2: attaching a volume to maver
** Changed in: ubuntu-on-ec2
Importance: Undecided => Wishlist
** Changed in: ubuntu-on-ec2
Status: New => Triaged
--
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/665235
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Wishlist
--
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/665235
Title:
grub-legacy-ec2: attaching a volume to maveri
I've added that this "also effects" ubuntu-on-ec2. The reason being
that the images are created with lp:~ubuntu-on-ec2/vmbuilder/automated-
ec2-builds/ , and the vmbuilder-fixups has some code that would have to
change to get this sorted.
--
grub-legacy-ec2: attaching a volume to maverick instan