OK - and your floating ip 172.29.249.112 has access to the internet? > Am 02.02.2019 um 17:33 schrieb Alfredo De Luca <alfredo.deluca at gmail.com>: > > [root at freddo-5oyez3ot5pxi-master-0 scripts]# curl -s http://169.254.169.254/latest/meta-data/local-ipv4 <http://169.254.169.254/latest/meta-data/local-ipv4> > 10.0.0.5[root at freddo-5oyez3ot5pxi-master-0 scripts]# > > [root at freddo-5oyez3ot5pxi-master-0 scripts]# curl -s http://169.254.169.254/latest/meta-data/public-ipv4 <http://169.254.169.254/latest/meta-data/public-ipv4> > 172.29.249.112[root at freddo-5oyez3ot5pxi-master-0 scripts]# > > 172.29.249.112 is the Floating IP... which I use to connect to the master > > > > > On Sat, Feb 2, 2019 at 5:26 PM Clemens <clemens.hardewig at crandale.de <mailto:clemens.hardewig at crandale.de>> wrote: > Hi Alfredo, > > This is basics of Openstack: curl -s http://169.254.169.254/latest/meta-data/local-ipv4 <http://169.254.169.254/latest/meta-data/local-ipv4> is a request to the metadata service with its special IP address 169.254.169.254 <http://169.254.169.254/latest/meta-data/local-ipv4>, to obtain the local ip address; the second one to get the public ip address > It look like from remote that your network is not properly configured so that this information is not answered from metadata service successfully. What happens if you execute that command manually? > > BR C -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190202/8a70ea26/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3783 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190202/8a70ea26/attachment-0001.bin>