Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/853681 Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/9fba870f6be56df6da9b303c378a983813ac31a7 Submitter: "Zuul (22348)" Branch: master
commit 9fba870f6be56df6da9b303c378a983813ac31a7 Author: Fernando Royo <[email protected]> Date: Thu Aug 18 17:40:14 2022 +0200 Fix healthMonitor events affecting to unrelated LB When an ServiceMonitorUpdateEvent happens, only those affected pools, listeners or LBs need to update their operating_status. This patch fixes the propagation of the affected member_id to other loadbalancers, as the search variable once set was not restarted when starting the parsing of another LB. Closes-Bug: #1986977 Change-Id: Ifbc836c6247add940c6392b2eda11e7e240fd36a ** 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/1986977 Title: [ovn-octavia-provider] HealthMonitor affecting several LBs Status in neutron: Fix Released Bug description: HealthMonitor over a pool that share a member (over a different port) with another pool or indeed over a different LB is updating all pools involving the member notified on the ServiceMonitorUpdateEvent. In particular the information mixed is on NBDB, on the field external_ids. E.g A member 10.0.0.100 on LB1 over pool1 (port 80) Same member 10.0.0.100 on LB2 over pool2 (port 22) HM over pool1 if HM notifies an offline status for member over pool 80, both LBs are including the information about the member in ERROR state on the external_ids. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1986977/+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
