[OVN Octavia Provider] OVN provider status update failures can leave orphaned resources
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Brian Haley |
Bug Description
This is related to Octavia issue https:/
When the OVN Octavia Provider driver calls into octavia-lib to update the status of a loadbalancer, for example, the code in helper:
DEBUG ovn_octavia_
ERROR ovn_octavia_
ERROR ovn_octavia_
ERROR ovn_octavia_
ERROR ovn_octavia_
ERROR ovn_octavia_
ERROR ovn_octavia_
ERROR ovn_octavia_
ERROR ovn_octavia_
This is failing because the listener associated with the loadbalancer was not found, it's DB transaction was in-flight. That's the related Octavia issue from above, but a fix for that will not solve the problem.
A side-effect is this listener is now "stuck":
$ openstack loadbalancer listener delete 7033179d-
Load Balancer 2cc1d429-
The provider driver needs to retry the operation, typically even the very next call succeeds.
summary: |
[OVN Octavia Provider] OVN provider status update failures can leave - orphaned resourcess + orphaned resources |
Changed in neutron: | |
status: | New → Confirmed |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. opendev. org/759139
Review: https:/