*** This bug is a duplicate of bug 615545 ***
https://bugs.launchpad.net/bugs/615545
Just to make tracking easier, I'm marking this as a duplicat of bug
615545.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
*** This bug is a duplicate of bug 615545 ***
https://bugs.launchpad.net/bugs/615545
** This bug has been marked a duplicate of bug 615545
Instances launched in a VPC cannot access ec2.archive.ubuntu.com
--
You received this bug notification because you are a member of Ubuntu
Server
Note that I just launched the latest 10.04 64-bit instance-store AMI and
this issue is still around. ami-fbbf7892
Will this fix be backported to the LTS release? As we move our
infrastructure into VPC, this is becoming very important.
--
You received this bug notification because you are a
Can you please verify that maverick (or later) images have this issue?
Also, could you provide the output of:
python -c 'import boto.utils, pprint;
pprint.pprint(boto.utils.get_instance_metadata())'
** Changed in: cloud-init (Ubuntu Lucid)
Status: Confirmed = Incomplete
--
You received
This is fix-released in maverick and later (bug 615545).
The only supported release that it would be present on would be 10.04.
You reported this using ubuntu-bug on a 11.04 instance. Are you
actually stating that you saw this bug with that ami?
Eric's suggestion does seem reasonable. The only
To be clear, I marked this fix-releases as 10.10 and later it should not be an
issue.
Eric, if you did see this issue on 11.04, please let me know.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Sorry, I should have been clear in the original bug report that I was
submitting it on behalf of Amazon and another customer and did not
experience it myself on that particular instance or AMI.
Also, I'm not sure that lack of a public IP address as described in
#615545 is sufficient to determine
Excerpts from Eric Hammond's message of Fri Aug 12 23:42:37 UTC 2011:
Amazon recommends fixing this through DNS instead of through software on
the instance.
Instead of resolving eu-west-1.ec2.archive.ubuntu.com directly to an A
record of the internal IP address starting with 10., Canonical
cloud-init should probably detect that VPC is in use, and not assume
that these regional archives are accessible. Marking as importance High
(since it affects all VPC users), and Confirmed.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = High
** Changed in: cloud-init (Ubuntu)
Amazon recommends fixing this through DNS instead of through software on
the instance.
Instead of resolving eu-west-1.ec2.archive.ubuntu.com directly to an A
record of the internal IP address starting with 10., Canonical should
change it to resolve to a CNAME of the external elastic IP address
--
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/824947
Title:
EC2 apt repository DNS resolution on VPC instances
To manage notifications about this bug go to:
11 matches
Mail list logo
