Revision history [back]

click to hide/show revision 1
initial version

I finally have figured out which was the problem.

The problem was related with security groups, by default there is a security group named "default" that allows egress connectivity to other systems running the same security group.

Users in one of our tenants have created a security group that only allows ingress ssh connections, so when the instance boots up and try to connect to the metadata proxy (169.254.169.254) it can't because of the security group rules.

In order to solve this problem is as easy as allow egress HTTP connectivity to 169.254.169.254 in any of the SG assigned to your instances or assign the "default" SG to your instances.

Thank you all!

I finally have figured out which was the problem.

The problem was related with security groups, by default there is a security group named "default" that allows egress connectivity to other systems running the same security group.

Users in one of our tenants have created a security group that only allows ingress ssh connections, so when the instance boots up and try to connect to the metadata proxy (169.254.169.254) it can't because of the security group rules.

In order to solve this problem is as easy as allow egress HTTP connectivity to 169.254.169.254 in any of the SG assigned to your instances or assign the "default" SG to your instances.

I recommend you to check out this link in order to understand how metadata proxy works: http://techbackground.blogspot.com.es/2013/06/metadata-via-quantum-router.html

Thank you all!