Please checkout the endpoint list if you have set it properly and check the cinder and nova conf files if it's set to glance properly On 03-Mar-2017 7:50 PM, "MarginHu" wrote: > Public bug reported: > > Hi Guys, > > It reports when I run the "init-runonce" script after deployed > successfully and run "post-deloy". > > Unable to establish connection to http://192.168.101.254:9292/v2/images: > HTTPConnectionPool(host='192.168.101.254', port=9292): Max retries > exceeded with url: /v2/images (Caused by > NewConnectionError(' object at 0x2c49510>: Failed to establish a new connection: [Errno 113] > No route to host',)) > > > kolla_external_vip_address: "192.168.101.254" > > kola 192.168.101.16 (deploy node) > kode0 192.168.101.20 (controller node) > kode1 192.168.101.21 (controller node) > kode3 192.168.101.23 (network node) > > I found 192.168.101.254 is located in Network node "kode3" , , > kode0 <-> kode1 is ok but kode0->kode3 or kode1->kode3 or kode3->kode0 is > not ok, > kola <->kode1 is ok. > > [root@kola neutron]# ip r > default via 192.168.122.1 dev eth0 > 169.254.0.0/16 dev eth0 scope link metric 1002 > 169.254.0.0/16 dev eth1 scope link metric 1003 > 169.254.0.0/16 dev eth2 scope link metric 1427 > 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 > 192.168.101.0/24 dev eth2 proto kernel scope link src 192.168.101.16 > 192.168.103.0/24 dev eth1 proto kernel scope link src 192.168.103.16 > 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.16 > [root@kola neutron]# > > > [root@kode0 kolla]# ip r > default via 192.168.122.1 dev eth5 > 169.254.0.0/16 dev eth0 scope link metric 1002 > 169.254.0.0/16 dev eth1 scope link metric 1003 > 169.254.0.0/16 dev eth2 scope link metric 1004 > 169.254.0.0/16 dev eth3 scope link metric 1005 > 169.254.0.0/16 dev eth4 scope link metric 1006 > 169.254.0.0/16 dev eth5 scope link metric 1007 > 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 > 192.168.101.0/24 dev eth2 proto kernel scope link src 192.168.101.20 > 192.168.102.0/24 dev eth1 proto kernel scope link src 192.168.102.20 > 192.168.103.0/24 dev eth0 proto kernel scope link src 192.168.103.20 > 192.168.104.0/24 dev eth3 proto kernel scope link src 192.168.104.20 > 192.168.106.0/24 dev eth4 proto kernel scope link src 192.168.106.20 > 192.168.122.0/24 dev eth5 proto kernel scope link src 192.168.122.20 > > [root@kode0 kolla]# ping -c 3 192.168.101.23 > PING 192.168.101.23 (192.168.101.23) 56(84) bytes of data. > ^C > --- 192.168.101.23 ping statistics --- > 3 packets transmitted, 0 received, 100% packet loss, time 1999ms > > [root@kode0 kolla]# > [root@kode0 kolla]# ping 192.168.101.21 > PING 192.168.101.21 (192.168.101.21) 56(84) bytes of data. > 64 bytes from 192.168.101.21: icmp_seq=1 ttl=64 time=0.608 ms > 64 bytes from 192.168.101.21: icmp_seq=2 ttl=64 time=0.388 ms > ^C > --- 192.168.101.21 ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 1000ms > rtt min/avg/max/mdev = 0.388/0.498/0.608/0.110 ms > [root@kode0 kolla]# > > [root@kode3 kolla]# ip r > default via 192.168.122.1 dev eth5 > 169.254.0.0/16 dev eth0 scope link metric 1002 > 169.254.0.0/16 dev eth1 scope link metric 1003 > 169.254.0.0/16 dev eth2 scope link metric 1004 > 169.254.0.0/16 dev eth3 scope link metric 1005 > 169.254.0.0/16 dev eth4 scope link metric 1006 > 169.254.0.0/16 dev eth5 scope link metric 1007 > 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 > 192.168.101.0/24 dev eth2 proto kernel scope link src 192.168.101.23 > 192.168.102.0/24 dev eth1 proto kernel scope link src 192.168.102.23 > 192.168.103.0/24 dev eth0 proto kernel scope link src 192.168.103.23 > 192.168.104.0/24 dev eth3 proto kernel scope link src 192.168.104.23 > 192.168.106.0/24 dev eth4 proto kernel scope link src 192.168.106.23 > 192.168.122.0/24 dev eth5 proto kernel scope link src 192.168.122.23 > [root@kode3 kolla]# ip a show eth2 > 4: eth2: mtu 1500 qdisc pfifo_fast > master ovs-system state UP qlen 1000 > link/ether 52:54:00:4d:c1:8c brd ff:ff:ff:ff:ff:ff > inet 192.168.101.23/24 brd 192.168.101.255 scope global eth2 > valid_lft forever preferred_lft forever > inet 192.168.101.254/32 scope global eth2 > valid_lft forever preferred_lft forever > inet6 fe80::5054:ff:fe4d:c18c/64 scope link > valid_lft forever preferred_lft forever > [root@kode3 kolla]# > > [root@kode3 kolla]# ping 192.168.101.21 -c 2 > PING 192.168.101.21 (192.168.101.21) 56(84) bytes of data. > >From 192.168.101.23 icmp_seq=1 Destination Host Unreachable > >From 192.168.101.23 icmp_seq=2 Destination Host Unreachable > > --- 192.168.101.21 ping statistics --- > 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 999ms > pipe 2 > [root@kode3 kolla]# ping 192.168.101.254 -c 2 > PING 192.168.101.254 (192.168.101.254) 56(84) bytes of data. > 64 bytes from 192.168.101.254: icmp_seq=1 ttl=64 time=0.046 ms > 64 bytes from 192.168.101.254: icmp_seq=2 ttl=64 time=0.044 ms > > --- 192.168.101.254 ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 1000ms > rtt min/avg/max/mdev = 0.044/0.045/0.046/0.001 ms > [root@kode3 kolla]# > > ** Affects: kolla > Importance: Undecided > Status: New > > -- > You received this bug notification because you are subscribed to kolla. > https://bugs.launchpad.net/bugs/1669797 > > Title: > report "no route" when connect kolla_external_vip_address and port > 9292 > > Status in kolla: > New > > Bug description: > Hi Guys, > > It reports when I run the "init-runonce" script after deployed > successfully and run "post-deloy". > > Unable to establish connection to > http://192.168.101.254:9292/v2/images: > HTTPConnectionPool(host='192.168.101.254', port=9292): Max retries > exceeded with url: /v2/images (Caused by > NewConnectionError(' object at 0x2c49510>: Failed to establish a new connection: [Errno > 113] No route to host',)) > > > kolla_external_vip_address: "192.168.101.254" > > kola 192.168.101.16 (deploy node) > kode0 192.168.101.20 (controller node) > kode1 192.168.101.21 (controller node) > kode3 192.168.101.23 (network node) > > I found 192.168.101.254 is located in Network node "kode3" , , > kode0 <-> kode1 is ok but kode0->kode3 or kode1->kode3 or kode3->kode0 > is not ok, > kola <->kode1 is ok. > > [root@kola neutron]# ip r > default via 192.168.122.1 dev eth0 > 169.254.0.0/16 dev eth0 scope link metric 1002 > 169.254.0.0/16 dev eth1 scope link metric 1003 > 169.254.0.0/16 dev eth2 scope link metric 1427 > 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 > 192.168.101.0/24 dev eth2 proto kernel scope link src 192.168.101.16 > 192.168.103.0/24 dev eth1 proto kernel scope link src 192.168.103.16 > 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.16 > [root@kola neutron]# > > > [root@kode0 kolla]# ip r > default via 192.168.122.1 dev eth5 > 169.254.0.0/16 dev eth0 scope link metric 1002 > 169.254.0.0/16 dev eth1 scope link metric 1003 > 169.254.0.0/16 dev eth2 scope link metric 1004 > 169.254.0.0/16 dev eth3 scope link metric 1005 > 169.254.0.0/16 dev eth4 scope link metric 1006 > 169.254.0.0/16 dev eth5 scope link metric 1007 > 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 > 192.168.101.0/24 dev eth2 proto kernel scope link src 192.168.101.20 > 192.168.102.0/24 dev eth1 proto kernel scope link src 192.168.102.20 > 192.168.103.0/24 dev eth0 proto kernel scope link src 192.168.103.20 > 192.168.104.0/24 dev eth3 proto kernel scope link src 192.168.104.20 > 192.168.106.0/24 dev eth4 proto kernel scope link src 192.168.106.20 > 192.168.122.0/24 dev eth5 proto kernel scope link src 192.168.122.20 > > [root@kode0 kolla]# ping -c 3 192.168.101.23 > PING 192.168.101.23 (192.168.101.23) 56(84) bytes of data. > ^C > --- 192.168.101.23 ping statistics --- > 3 packets transmitted, 0 received, 100% packet loss, time 1999ms > > [root@kode0 kolla]# > [root@kode0 kolla]# ping 192.168.101.21 > PING 192.168.101.21 (192.168.101.21) 56(84) bytes of data. > 64 bytes from 192.168.101.21: icmp_seq=1 ttl=64 time=0.608 ms > 64 bytes from 192.168.101.21: icmp_seq=2 ttl=64 time=0.388 ms > ^C > --- 192.168.101.21 ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 1000ms > rtt min/avg/max/mdev = 0.388/0.498/0.608/0.110 ms > [root@kode0 kolla]# > > [root@kode3 kolla]# ip r > default via 192.168.122.1 dev eth5 > 169.254.0.0/16 dev eth0 scope link metric 1002 > 169.254.0.0/16 dev eth1 scope link metric 1003 > 169.254.0.0/16 dev eth2 scope link metric 1004 > 169.254.0.0/16 dev eth3 scope link metric 1005 > 169.254.0.0/16 dev eth4 scope link metric 1006 > 169.254.0.0/16 dev eth5 scope link metric 1007 > 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 > 192.168.101.0/24 dev eth2 proto kernel scope link src 192.168.101.23 > 192.168.102.0/24 dev eth1 proto kernel scope link src 192.168.102.23 > 192.168.103.0/24 dev eth0 proto kernel scope link src 192.168.103.23 > 192.168.104.0/24 dev eth3 proto kernel scope link src 192.168.104.23 > 192.168.106.0/24 dev eth4 proto kernel scope link src 192.168.106.23 > 192.168.122.0/24 dev eth5 proto kernel scope link src 192.168.122.23 > [root@kode3 kolla]# ip a show eth2 > 4: eth2: mtu 1500 qdisc pfifo_fast > master ovs-system state UP qlen 1000 > link/ether 52:54:00:4d:c1:8c brd ff:ff:ff:ff:ff:ff > inet 192.168.101.23/24 brd 192.168.101.255 scope global eth2 > valid_lft forever preferred_lft forever > inet 192.168.101.254/32 scope global eth2 > valid_lft forever preferred_lft forever > inet6 fe80::5054:ff:fe4d:c18c/64 scope link > valid_lft forever preferred_lft forever > [root@kode3 kolla]# > > [root@kode3 kolla]# ping 192.168.101.21 -c 2 > PING 192.168.101.21 (192.168.101.21) 56(84) bytes of data. > From 192.168.101.23 icmp_seq=1 Destination Host Unreachable > From 192.168.101.23 icmp_seq=2 Destination Host Unreachable > > --- 192.168.101.21 ping statistics --- > 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time > 999ms > pipe 2 > [root@kode3 kolla]# ping 192.168.101.254 -c 2 > PING 192.168.101.254 (192.168.101.254) 56(84) bytes of data. > 64 bytes from 192.168.101.254: icmp_seq=1 ttl=64 time=0.046 ms > 64 bytes from 192.168.101.254: icmp_seq=2 ttl=64 time=0.044 ms > > --- 192.168.101.254 ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 1000ms > rtt min/avg/max/mdev = 0.044/0.045/0.046/0.001 ms > [root@kode3 kolla]# > > To manage notifications about this bug go to: > https://bugs.launchpad.net/kolla/+bug/1669797/+subscriptions >