Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/865003 Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/e32049135a35f45720a3a221f3f90248bdd0ac52 Submitter: "Zuul (22348)" Branch: master
commit e32049135a35f45720a3a221f3f90248bdd0ac52 Author: Fernando Royo <[email protected]> Date: Fri Nov 18 10:47:50 2022 +0100 Add support for HM on a fullypopulated load balancers Octavia API allows to create fully populated load balancers with a single call, and the pools included in that call could include HM. OVN-octavia-provider was not implementing this option and only the loadbalancer/listener(s)/pool(s)/member(s) were created, keeping the HM at the Octavia API as PENDING_CREATE. This also generated leftovers when trying to delete the loadbalancer with the --cascade option. Closes-Bug: #1997094 Change-Id: Ic24a0c1622c0aac2a40542cadf91a1bc47de1de6 ** 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/1997094 Title: [ovn-octavia-provider] HM created at fully populated loadbalancer stuck in PENDING_CREATE Status in neutron: Fix Released Bug description: When try to create a health monitor on OVN LBs using the API to create fully populated loadbalancers, where the pool object will include the information about the HM to be created. These become stuck in PENDING_CREATE and is not functional at all. If I delete it, the LB it was tied to will become stuck in PENDING_UPDATE. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1997094/+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
