[ovn-octavia-provider] HM created at fully populated loadbalancer stuck in PENDING_CREATE
Bug #1997094 reported by
Fernando Royo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Fernando Royo |
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.
Changed in neutron: | |
assignee: | nobody → Fernando Royo (froyoredhat) |
Changed in neutron: | |
status: | New → In Progress |
Changed in neutron: | |
importance: | Undecided → Medium |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/c/openstack /ovn-octavia- provider/ +/865003 /opendev. org/openstack/ ovn-octavia- provider/ commit/ e32049135a35f45 720a3a221f3f902 48bdd0ac52
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit e32049135a35f45 720a3a221f3f902 48bdd0ac52
Author: Fernando Royo <email address hidden>
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 provider was not implementing this option and only listener( s)/pool( s)/member( s) were created,
a single call, and the pools included in that call could include
HM. OVN-octavia-
the loadbalancer/
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: Ic24a0c1622c0aa c2a40542cadf91a 1bc47de1de6