Network problems after compute node reboot

asked 2018-05-30 00:25:53 -0500

ICBeter gravatar image

We rebooted a compute node while running an instance on it. After the reboot the network of this instance did not work. I could not ping the internal address nor the floating IP. Rebooting, Hard resetting... nothing helped. I had to recreate the instance based on the volume. Then it worked again.

What could been the problem?

It is Queens running on Ubuntu 16.04 with networking done by Neutron.

edit retag flag offensive close merge delete


Before rebuilding the instance I would first have tried to just detach and reattach the instance's interface. Did you check if neutron (linuxbridge or ovs, whatever you're using) was up and running on the compute node? Did you check with tcpdump where the packages got lost?

eblock gravatar imageeblock ( 2018-05-30 01:54:05 -0500 )edit

Yes, I tried detaching and reattaching the interface. When I created a new instance, everything worked, so linuxbridge on the compute node must be ok. If that happens again I will check with tcpdump. Anyone any other idea?

ICBeter gravatar imageICBeter ( 2018-05-30 08:46:07 -0500 )edit

When you reattached the interface did you check if the instance really had an interface? With something like vnc console? Sounds like the instance's interface configuration could have got lost. Was it running during compute reboot?

eblock gravatar imageeblock ( 2018-05-31 01:47:32 -0500 )edit