Comment 8 for bug 672986

Revision history for this message
Scott Moser (smoser) wrote :

- I tested maverick with the following:
  us-east-1 ami-a6f504cf canonical ubuntu-maverick-10.10-i386-server-20101225
- sudo mkdir /mnt/creds && sudo chown ubuntu:ubuntu /mnt/creds
  . /mnt/creds # creds file set up to have necessary environment vars
- add proposed and install/upgrade package
  $ mirror=$(awk '$0 ~ /^deb / { print $2 ; exit(0); }' /etc/apt/sources.list)
  $ echo "deb ${mirror} $(lsb_release -sc)-proposed main universe multiverse" | sudo tee -a /etc/apt/sources.list
  $ echo "deb ${mirror} $(lsb_release -sc) multiverse" | sudo tee -a /etc/apt/sources.list
  $ sudo apt-get update
  $ apt-cache policy ec2-ami-tools
    ec2-ami-tools:
      Installed: (none)
      Candidate: 1.3.49953-0ubuntu1.1
      Version table:
         1.3.49953-0ubuntu1.1 0
            500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ maverick-proposed/multiverse i386 Packages
  $ sudo apt-get install ec2-ami-tools ec2-api-tools
- dest=/mnt/dest
- sudo rm -Rf "${dest}" && sudo mkdir -p "${dest}" && cd "${dest}"
- name=ec2-ami-rebundle-$(lsb_release -sc).img
- arch=$(uname -m) ; [ "${arch}" = "i686" ] && arch=i386
- sudo ec2-bundle-vol \
   --cert "${EC2_CERT}" --privatekey "${EC2_PRIVATE_KEY}" \
   --user "${EC2_USER_ID}" \
   --arch ${arch} \ --destination /mnt/dest \
   --arch "${arch}" \
   --prefix "${name}" \
   --size 2048
- verify that / and target have the same fs info:
 $ sudo blkid ${name} /dev/sda1
 ec2-ami-rebundle-maverick.img: LABEL="uec-rootfs" UUID="7742f6ee-e492-4019-a70f-877c43562a7b" TYPE="ext4"
 /dev/sda1: LABEL="uec-rootfs" UUID="7742f6ee-e492-4019-a70f-877c43562a7b" TYPE="ext4"
- upload/register
  bucket=smoser-test
  $ ec2-upload-bundle \
   --access-key ${EC2_ACCESS_KEY} --secret-key ${EC2_SECRET_KEY} \
   --bucket ${bucket} \
   --manifest ${name}.manifest.xml
  $ ec2-register --name ${name%.img} ${bucket}/${name}.manifest.xml
- run the new instance, and verify you can connect
  ec2-run-instances <new_ami>
  ssh ubuntu@....

This all worked fine. Prior to this bug being fixed, the filesystem would have always been ext3, and have had no label and a different uuid than this.