network is unreachable in instance

asked 2018-06-15 08:43:07 -0500

JC gravatar image

I have similar problem as discussed in : https://ask.openstack.org/en/question/80462/network-is-unreachable-in-instance/ (https://ask.openstack.org/en/question...)

I didn't get the solution, so asking for some help: We have 3 controller nodes connected to 12 compute nodes. I was working fine, we were facing some issues connecting to floating ips. After some time, complete network went down. Not sure what is the problem. If you need more logs , please let me know. I will provide:

[Thu Jun 14 14:38:57] root@:~# node-ping-check

 Ping check of all service-ip, vm-ip, data-ip and floating-ip, ping
 status result after ip, 1/0 = alive/dead

 command start time 2018-06-14 14:39:00

 node    service-ip        vm-ip          data-ip        floating-ip
---------------------------------------------------------------------
 h002   10.1.12.102 1   10.2.12.102 1   10.3.13.102 1   10.4.13.102 1 (controller 1)
 h003   10.1.12.103 1   10.2.12.103 1   10.3.13.103 1   10.4.13.103 1 (controller 2)
 h004   10.1.12.104 1   10.2.12.104 1   10.3.13.104 1   10.4.13.104 1 (controller 3 + Network node)
 h005   10.1.12.105 1   10.2.12.105 1   10.3.13.105 1   10.4.13.105 0
 h006   10.1.12.106 1   10.2.12.106 1   10.3.13.106 1   10.4.13.106 0
 h007   10.1.12.107 1   10.2.12.107 1   10.3.13.107 1   10.4.13.107 0
 h008   10.1.12.108 1   10.2.12.108 1   10.3.13.108 1   10.4.13.108 0
 h009   10.1.12.109 1   10.2.12.109 1   10.3.13.109 1   10.4.13.109 0
 h010   10.1.12.110 1   10.2.12.110 1   10.3.13.110 1   10.4.13.110 0
 h011   10.1.14.111 1   10.2.14.111 1   10.3.15.111 1   10.4.15.111 0
 h012   10.1.14.112 1   10.2.14.112 1   10.3.15.112 1   10.4.15.112 0
 h013   10.1.14.113 1   10.2.14.113 1   10.3.15.113 1   10.4.15.113 0
 h014   10.1.14.114 1   10.2.14.114 1   10.3.15.114 1   10.4.15.114 0
 h015   10.1.14.115 1   10.2.14.115 1   10.3.15.115 1   10.4.15.115 0
 h016   10.1.14.116 0   10.2.14.116 0   10.3.15.116 0   10.4.15.116 0  ( Down because of hardware issue)
 h017   10.1.14.117 1   10.2.14.117 1   10.3.15.117 1   10.4.15.117 0

[Thu Jun 14 14:39:39] root@:~#

I tired to bring br-ex to fix the problem by associating with eth3 ip . If i don't do this ping to 10.4.13.104 ... (more)

edit retag flag offensive close merge delete

Comments

What is the output of ip netns on the controllers?

woltjert gravatar imagewoltjert ( 2018-07-10 16:32:12 -0500 )edit