NSXv: LB pool delete failure while binding missing
When pool binding is missing, LBaaS call shouldn't fail, but exit gracefully. Change-Id: I6174880f38f8ebbe4def931053ee47880a89426c
This commit is contained in:
parent
659ea71520
commit
9088cb2b31
|
@ -155,6 +155,11 @@ class EdgePoolManager(base_mgr.EdgeLoadbalancerBaseManager):
|
||||||
context.session, lb_id, pool.id)
|
context.session, lb_id, pool.id)
|
||||||
|
|
||||||
edge_id = lb_binding['edge_id']
|
edge_id = lb_binding['edge_id']
|
||||||
|
if not pool_binding:
|
||||||
|
self.lbv2_driver.pool.successful_completion(
|
||||||
|
context, pool, delete=True)
|
||||||
|
return
|
||||||
|
|
||||||
edge_pool_id = pool_binding['edge_pool_id']
|
edge_pool_id = pool_binding['edge_pool_id']
|
||||||
|
|
||||||
listeners_to_update = []
|
listeners_to_update = []
|
||||||
|
|
Loading…
Reference in New Issue