Comment 8 for bug 1798690

Thanks Sean! I will have to look at the hosts again, but it appears the OVS configuration does not get migrated from source to target host. Instead, the OVS configuration remains on the source host. I was able to migrate the VM "back" to the source and the internal network connectivity started to work again. I was looking at the OVS rules, and the rules (flows) still exist in the vswitch on the source host.

I will try the hard reboot and see if it does anything.

Kolla Ansible, by default, installs OVS, but I'm not positive whether OVS is used for security groups. I tend to remember looking at this a while back and believe it has Neutron configure iptables. Is there anything specific in the configuration that I can check for you?

I will check on the port status and admin status, but I'm almost positive the port (in the guest) is "up up". I have seen floating IPs work, but internal IPs "not" work, and both use the same port, thus why I say this, but I will confirm exactly in my next round of tests.

I have another bug submitted that is a timing bug during a cold migration - see here:
https://bugs.launchpad.net/nova/+bug/1799309

So, maybe there is a timing issue during live migration too, that produces no error, but fails to migrate OVS flows?

Eric