** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/634102/+attachment/1560941/+files/Dependencies.txt
** Summary changed: - cloud-init writes ephemeral0 entry in /etc/fstab on t1.micro type + t1.micro instances hang on reboot ** Description changed: Binary package hint: cloud-init - on Amazon's new t1.micro instance type, there is no ephemeral storage at - all. + on Amazon's new t1. instance type, there is no ephemeral storage at all. + If you run a ubuntu ebs image on instance type t1.micro and reboot, it + will not come back up. mountall will wait indefinitely for /dev/sda2, + which is never going to be present. cloud-init is basically hard coded to expect an 'ephemeral0', while other ephemeral devices are more dynamic. Our images are registered with block-device-mapping indicating ephemeral0, so the metadata service will include ephemeral0 even though there is not one on the instance itself. We need to do one of 2 things here: a.) add 'nobootwait' for the ephemeral0 device (/dev/sda2 in this case) b.) not write a entry in /etc/fstab (or comment it out) if that device is not present on the first boot. + + There are 2 easy workarounds for this: + 1.) sudo sed -i.dist '\,/dev/sda1,s,^,#,' /etc/fstab + 2.) launch instance with cloud-config metadata containing: + #cloud-config + mounts: + - [ ephemeral0 ] ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: cloud-init 0.5.10-0ubuntu1.2 ProcVersionSignature: User Name 2.6.32-308.15-ec2 2.6.32.15+drm33.5 Uname: Linux 2.6.32-308-ec2 i686 Architecture: i386 Date: Thu Sep 9 14:42:21 2010 Ec2AMI: ami-1234de7b Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: t1.micro Ec2Kernel: aki-5037dd39 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: - PATH=(custom, user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: cloud-init ** Description changed: Binary package hint: cloud-init on Amazon's new t1. instance type, there is no ephemeral storage at all. If you run a ubuntu ebs image on instance type t1.micro and reboot, it will not come back up. mountall will wait indefinitely for /dev/sda2, which is never going to be present. cloud-init is basically hard coded to expect an 'ephemeral0', while other ephemeral devices are more dynamic. Our images are registered with block-device-mapping indicating ephemeral0, so the metadata service will include ephemeral0 even though there is not one on the instance itself. We need to do one of 2 things here: a.) add 'nobootwait' for the ephemeral0 device (/dev/sda2 in this case) b.) not write a entry in /etc/fstab (or comment it out) if that device is not present on the first boot. There are 2 easy workarounds for this: - 1.) sudo sed -i.dist '\,/dev/sda1,s,^,#,' /etc/fstab + 1.) sudo sed -i.dist '\,/dev/sda2,s,^,#,' /etc/fstab 2.) launch instance with cloud-config metadata containing: #cloud-config mounts: - - [ ephemeral0 ] + - [ ephemeral0 ] ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: cloud-init 0.5.10-0ubuntu1.2 ProcVersionSignature: User Name 2.6.32-308.15-ec2 2.6.32.15+drm33.5 Uname: Linux 2.6.32-308-ec2 i686 Architecture: i386 Date: Thu Sep 9 14:42:21 2010 Ec2AMI: ami-1234de7b Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: t1.micro Ec2Kernel: aki-5037dd39 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init -- t1.micro instances hang on reboot https://bugs.launchpad.net/bugs/634102 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