[Openstack-operators] [Openstack] Recovering from full outage

Torin Woltjer torin.woltjer at granddial.com
Thu Jul 12 14:21:17 UTC 2018

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: via dev ens3 proto dhcp metric 100.
curl returns information, for example; 

On the second instance:
The route exists: via dev eth0
curl fails;
curl: (7) Failed to connect to 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

From: John Petrini <jpetrini at coredial.com>
Sent: 7/12/18 9:16 AM
To: torin.woltjer at granddial.com
Cc: thangam.arunx at gmail.com, OpenStack Operators <openstack-operators at lists.openstack.org>, OpenStack Mailing List <openstack at lists.openstack.org>
Subject: Re: [Openstack-operators] [Openstack] Recovering from full outage
Are you instances receiving a route to the metadata service ( from DHCP? Can you curl the endpoint? curl

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20180712/269e34d2/attachment.html>

More information about the OpenStack-operators mailing list