Comment 15 for bug 1732543

This is great news!

Thank you!

On Thu, Dec 14, 2017 at 2:41 PM Florian Haas <email address hidden> wrote:

> To everyone involved in fixing this — you really made a difference.
> Thanks a lot!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1732543
>
> Title:
> HA network tenant network fails upon router delete
>
> Status in neutron:
> Fix Released
>
> Bug description:
> Openstack version: Pike
> Openvswitch version: 2.7
>
> Let's say I have a Openstack project where I've created 2 routers (R1
> & R2). Both routers are configured as L3-HA on pair of network nodes.
> Each of the 2 routers has an Active and a Passive namespace on each
> network node. Neutron creates a unique HA network for each project
> that allows the Active router to send VRRP messages to the Passive
> router. When using vxlan for the "tenant_network_type" a vxlan vni is
> assigned to the said HA network that allows that VRRP east/west
> traffic make it between the 2 network nodes.
>
> The assigned vni is discovered using "openstack network show UUID"
>
> Now, if we delete, for example, router R2, R1 will still need the HA
> network with its associated vni so VRRP communication can continue to
> work. The nature of this discovered bug is that if 1 router (either R1
> or R2, doesn't matter) is deleted the vni gets removed from a HA
> network entirely. At this point, the remaining router (R1) will
> continue to work, despite the HA network not functioning any more.
>
> After the network nodes get restarted though, the broken config is
> loaded and the routers cease to function per the HA network lacking a
> vni assignment.
>
> This problem didn't start happening until we upgraded to Pike.
>
> See attached for proposed fix.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/neutron/+bug/1732543/+subscriptions
>