Two more things to note
1.) I just opened bug 672986 that euca-bundle-vol should copy uuid
2.) above, I stated that grub2 loads the kernel on uec and pv-grub. It may
have similar issues.
** Description changed:
- Binary package hint: cloud-init
+ Binary package hint: grub-legacy-ec2
I booted a maverick instance, modified it a bit, and created a snapshot
of that volume.
I then, booted another maverick instance like:
run-instances ami-548c783d --instance-type t1.micro --block-device-mapping
/dev/sdh=${SNAPSHOT}:${SIZE}
the surprising result was that the instance booted with root = /dev/sdh.
The reason for that is that menu.lst in the instance says:
kernel /boot/vmlinuz-2.6.35-22-virtual root=LABEL=uec-rootfs ro
console=hvc0
initrd /boot/initrd.img-2.6.35-22-virtual
In this instance, there were, then 2 filesystems that had LABEL=uec-rootfs.
The kernel just chose /dev/sdh.
update-grub-legacy-ec2 is what writes the 'LABEL=uec-rootfs'.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: cloud-init 0.5.15-0ubuntu3
ProcVersionSignature: User Name 2.6.35-22.33-virtual 2.6.35.4
Uname: Linux 2.6.35-22-virtual x86_64
Architecture: amd64
Date: Fri Oct 22 17:19:50 2010
Ec2AMI: ami-548c783d
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1c
Ec2InstanceType: t1.micro
Ec2Kernel: aki-427d952b
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
SourcePackage: cloud-init
** Summary changed:
- attaching a volume to maverick instance may boot off it
+ grub-legacy-ec2: attaching a volume to maverick instance may boot off it
** Also affects: ubuntu-on-ec2
Importance: Undecided
Status: New
--
grub-legacy-ec2: attaching a volume to maverick instance may boot off it
https://bugs.launchpad.net/bugs/665235
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
