Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/860779 Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/464cb97fadd7134814cadd171b4de8cd2eda530e Submitter: "Zuul (22348)" Branch: master
commit 464cb97fadd7134814cadd171b4de8cd2eda530e Author: Luis Tomas Bolivar <[email protected]> Date: Mon Oct 10 17:13:27 2022 +0200 Ensure LB are removed from LS not connected to the LB LR Once the logical_switch (neutron subnet) is removed from the logical_router (neutron router) where the OVN-LB VIP and members are connected to, there is no need to keep the LB added to that logical_switch Closes-Bug: #1992356 Change-Id: I86aba3eee88b3da3cae7b57da2eabc6c3cb5d953 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1992356 Title: [ovn-octavia-provider] LS has LB leftover after being removed from the router Status in neutron: Fix Released Bug description: In order to have ovn-lb properly configured it is needed to include the loadbalancer in all the logical_switches connected to the logical_router where the VIP and the members are connected to. With that, in the next scenario: - LR1 - LS1 and LS2 connected to LR1 - OVN-LB1 with VIP and the members on LS1 The LB is added to both LR1, and LS1 and LS2. However, if LS2 is detached from the LR1, the OVN-LB1 remains added to the LS2 while it should be removed To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1992356/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
