[ovn-octavia-provider] Updating status on incorrect pool when HM delete
Bug #2024912 reported by
Fernando Royo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
New
|
Medium
|
Fernando Royo | ||
Bug Description
When a Health Monitor is deleted from a LB with multiples pools, the HM is deleted correctly. But sometimes a random pool (not related to the HM being deleted) keeps in PENDING_UPDATE provisioning_
Look like the status update sending to Octavia API was referencing a pool not related to the HM deleted.
| Changed in neutron: | |
| assignee: | nobody → Fernando Royo (froyoredhat) |
| Changed in neutron: | |
| importance: | Undecided → Medium |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/ovn-octavia-provider 2.2.0 | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/ovn-octavia-provider 5.0.0.0rc1 | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/ovn-octavia-provider 3.1.2 | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/ovn-octavia-provider wallaby-eom | #4 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/ovn-octavia-provider xena-eom | #5 |
To post a comment you must log in.
This issue was fixed in the openstack/