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

[Felipe Reyes]

The workaround used to know if the instance is inside a VPC isn't
working for me, I launched a EC2 instance and I assigned an Elastic IP
(all these using cloud formation), when cloud-init gets the metadata
this is what it gets:

# curl http://169.254.169.254/latest/meta-data/
ami-id
ami-launch-index
ami-manifest-path
block-device-mapping/
hostname
instance-action
instance-id
instance-type
kernel-id
local-hostname
local-ipv4
mac
metrics/
network/
placement/
profile
public-ipv4
public-keys/
reservation-id
security-groups

$ curl http://169.2st/meta-data/public-ipv4
184.72.x.x

As you can see the field public-ipv4 appears in the metadata, so cloud-
init thinks the instance isn't running in a VPC and sets the apt mirror
to us-east1... and it takes me to the original situation. No access to
the repositories.

I fixed this behavior with the sugested key in cloud-config.yaml
(apt_mirror: http://us.archive.ubuntu.com/ubuntu/).

-- 
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