Yes, Billy Olsen, we are a little in doubt about this (https://bugs.launchpad.net/neutron/+bug/1927868/comments/18) as well.
We have been observing such non functioning gateways on our Train installation occasionally also before this patch / update. Usually a "clear gateway" and a recreation via the Horizon GUI by the user fixed this - one more reason to pursue the idea of a race condition as it then works on another attempt. Also killing the master keepalived did work as it then switched over to another node usually just worked. With the recent change though, we appear to have had a larger number broken gateways after migrations and node reboots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
