I've verified this on both
us-east-1 ami-1234de7b ebs/ubuntu-lucid-10.04-i386-server-20100827
us-east-1 ami-1634de7f ebs/ubuntu-lucid-10.04-amd64-server-20100827
- launch instance
- ssh instance
- verify that '/etc/fstab' has an entry for "/mnt" whose device does not exist
i386:
| $ awk '$2 == "/mnt" { print $0 }' /etc/fstab
| /dev/sda2 /mnt auto defaults,comment=cloudconfig 0 0
| $ [ -b /dev/sda2 ] || echo "no"
| no
amd64:
| $ awk '$2 == "/mnt" { print $0 }' /etc/fstab
| /dev/sdb /mnt auto defaults,comment=cloudconfig 0 0
| $ [ -b /dev/sdb ] || echo "no"
| no
- enable proposed, update, install cloud-init
| $ l="deb http://archive.ubuntu.com/ubuntu lucid-proposed main"
| $ echo "$l" | sudo tee -a /etc/apt/sources.list
| $ sudo apt-get update && sudo apt-get install cloud-init
| $ dpkg-query --show cloud-init
| cloud-init 0.5.10-0ubuntu1.3
- Now, verify that the installation of the package has fixed /etc/fstab
Notice that 'nobootwait' has been added. In dpkg output, you will
also see a message like:
making ephemeral /dev/sda2 in /etc/fstab nobootwait (LP: #634102)
i386
| $ awk '$2 == "/mnt" { print $0 }' /etc/fstab
| /dev/sda2 /mnt auto defaults,comment=cloudconfig,nobootwait 0 0
amd64
| $ awk '$2 == "/mnt" { print $0 }' /etc/fstab
| /dev/sdb /mnt auto defaults,comment=cloudconfig,nobootwait 0 0
- Verify 'reboot', and that you can ssh back in
- Now, verify that cloud-init would write 'nobootwait' on first boot, by
removing all of /var/lib/cloud so cloud-init thinks this is a first boot
| $ sudo rm -Rf /var/lib/cloud && reboot
- ssh back in and check /etc/fstab
i386
| $ awk '$2 == "/mnt" { print $0 }' /etc/fstab
| /dev/sda2 /mnt auto defaults,nobootwait,comment=cloudconfig 0 0
amd64
| $ awk '$2 == "/mnt" { print $0 }' /etc/fstab
| /dev/sdb /mnt auto defaults,nobootwait,comment=cloudconfig 0 0
- reboot to test *that* written /etc/fstab, and connect again
** Tags added: verification-done
** Tags removed: verification-needed
--
t1.micro EC2 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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
