Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/874609 Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/569c9c011a2cc9e5f041633dde4a47257e4d8565 Submitter: "Zuul (22348)" Branch: master
commit 569c9c011a2cc9e5f041633dde4a47257e4d8565 Author: Fernando Royo <[email protected]> Date: Tue Feb 21 16:35:10 2023 +0100 Reset member provisioning status to NO_MONITOR when a HM is deleted At present, when a health monitor (HM) is created for a pool, the members of that pool are automatically set to ONLINE provisioning status, unless the HM identifies an ERROR during health checks. This patch addresses an issue where, after deleting an HM, the members should be reset to NO_MONITOR provisioning status, regardless of whether the HM had previously set them to ONLINE or ERROR status. Closes-Bug: #2007985 Change-Id: I02bcba61d0cbc9202a6e50b849f8d781fb825d49 ** 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/2007985 Title: [ovn-octavia-provider] restore the member provisioning status to NO_MONITOR after delete the HM Status in neutron: Fix Released Bug description: When a HM is creating over a pool, the members associated to it change theis provisioning_status to ONLINE, and if the health checks packets detects an error on communication it will move to ERROR. When the HM is deleted the provisioning status of those members should come back to NO_MONITOR, but now is keeping on the last status (ONLINE or ERROR) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2007985/+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
