[Bug 615545] Re: Instances launched in a VPC cannot access ec2.archive.ubuntu.com

Scott Moser smoser at ubuntu.com
Fri Jan 13 09:00:39 UTC 2012


I believe we talked once about doing the CNAME solution, and the
decision was made not to implement it.  The reason was (from memory)
that if we did, all requests would then hit external mirrors, and
subsequently we would have to open up all traffic to the ec2 mirrors
that canonical IS is running.  The decision was not to do that.

So, the other solution here is:
a.) SRU the fix in cloud-init to lucid
b.) wait until the s3 backed mirrors are live

B is expected inside of 30 days, and the SRU takes at least 2 weeks to get into the archive.
We expect that s3 backed mirrors will be open to the world, so this will not be a problem anymore.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/615545

Title:
  Instances launched in a VPC cannot access ec2.archive.ubuntu.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/615545/+subscriptions



More information about the Ubuntu-server-bugs mailing list