Comment 12 for bug 1077020

Luis, for testing with -proposed, I used the attached following cloud-config file passed in as user-data.
It adds -proposed and moves the ca-cert config module to run later in the process so the update has already occurred.

Just for reference, I launched instance like this:
$ EC2PRE=euca- ubuntu-ec2-run quantal daily --dry-run --user-data-file=/tmp/my.ud --key=brickies
# us-east-1/ebs/ubuntu-quantal-daily-amd64-server-20130109
euca-run-instances --user-data-file=/tmp/my.ud --key=brickies --instance-type=t1.micro ami-ed21a884

Then, in console output and /var/log/cloud-init-output.log I see:

Cloud-init v. 0.7 running 'modules:final' at Wed, 09 Jan 2013 14:26:23 +0000. Up 58.53 seconds.
Updating certificates in /etc/ssl/certs... Error opening Certificate cert-ec2.pem
140485162526368:error:02001002:system library:fopen:No such file or directory:bss_file.c:398:fopen('cert-ec2.pem','r')
140485162526368:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:400:
unable to load certificate
WARNING: cert-ec2.pem does not contain a certificate or CRL: skipping
1 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d....done.

The noise about invalid certificicate is due to bug 1085537.

Then, inside the instance:
$ ls -l /usr/lib/ssl/certs/ | grep -i cloud
lrwxrwxrwx 1 root root 23 Jan 9 14:26 b1d2b355.0 -> cloud-init-ca-certs.pem
lrwxrwxrwx 1 root root 23 Jan 9 14:26 cbbf81bb.0 -> cloud-init-ca-certs.pem
lrwxrwxrwx 1 root root 50 Jan 9 14:26 cloud-init-ca-certs.pem -> /usr/share/ca-certificates/cloud-init-ca-certs.crt