Public bug reported: Binary package hint: cloud-init
After the first time update-grub-legacy-ec2 runs inside an ec2 instance, the root will be specified by UUID. The initial images are hard coded to have root specified on the linux command line by LABEL, but after the first run, a UUID will appear. This is actually superior in some ways, but will negatively affect filesystem level rebundling (ie, in euca-bundle-vol). root=UUID=429ef293-0128-4c19-b194-4b9a2e4fe7a1 On ext2, the UUID can be written with 'tune2fs -U' or 'mke2fs -U' Some more thought needs to go into how to fix this correctly. The reason for choosing LABEL and/or UUID rather than 'root=/dev/sda1' was to be more like grub2, and to avoid disk naming issues (even though, on ec2, sda1 is probably a constant for the root device). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: grub-legacy-ec2 0.5.15-0ubuntu3 ProcVersionSignature: User Name 2.6.35-22.33-virtual 2.6.35.4 Uname: Linux 2.6.35-22-virtual i686 Architecture: i386 Date: Fri Nov 5 14:13:10 2010 Ec2AMI: ami-508c7839 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t1.micro Ec2Kernel: aki-407d9529 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 maverick -- grub-legacy-ec2 should not use UUID https://bugs.launchpad.net/bugs/671427 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs