I tested this on two instances. The first instance has existed since before I began having this issue. The second is created from a cirros test image.
On the first instance: The route exists: 169.254.169.254 via 172.16.1.1 dev ens3 proto dhcp metric 100. curl returns information, for example; `curl http://169.254.169.254/latest/meta-data/public-keys` 0=nextcloud On the second instance: The route exists: 169.254.169.254 via 172.16.1.1 dev eth0 curl fails; `curl http://169.254.169.254/latest/meta-data` curl: (7) Failed to connect to 169.254.169.254 port 80: Connection timed out I am curious why this is the case that one is able to connect but not the other. Both the first and second instances were running on the same compute node. Torin Woltjer Grand Dial Communications - A ZK Tech Inc. Company 616.776.1066 ext. 2006 www.granddial.com ---------------------------------------- From: John Petrini <jpetr...@coredial.com> Sent: 7/12/18 9:16 AM To: torin.wolt...@granddial.com Cc: thangam.ar...@gmail.com, OpenStack Operators <openstack-operators@lists.openstack.org>, OpenStack Mailing List <openst...@lists.openstack.org> Subject: Re: [Openstack-operators] [Openstack] Recovering from full outage Are you instances receiving a route to the metadata service (169.254.169.254) from DHCP? Can you curl the endpoint? curl http://169.254.169.254/latest/meta-data
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
