Associate floating IP after lb ACTIVE

There was a chance that the `device_owner` of VIP port changed to
`compute:None` which blocks the VIP subnet clean up, this patch fixed
that.

Change-Id: I39a63584793c1f0aca7a74f01649dd5618d5829e
Story: 2006551
Task: 36634
This commit is contained in:
Lingxian Kong 2019-09-15 23:05:44 +12:00
parent 7140479919
commit 2eba544d21
1 changed files with 6 additions and 6 deletions

View File

@ -51,6 +51,12 @@ class TrafficOperationsScenarioTest(test_base.LoadBalancerBaseTestWithCompute):
cls.mem_lb_client.cleanup_loadbalancer,
cls.lb_id)
waiters.wait_for_status(cls.mem_lb_client.show_loadbalancer,
cls.lb_id, const.PROVISIONING_STATUS,
const.ACTIVE,
CONF.load_balancer.lb_build_interval,
CONF.load_balancer.lb_build_timeout)
if CONF.validation.connect_method == 'floating':
port_id = lb[const.VIP_PORT_ID]
result = cls.lb_mem_float_ip_client.create_floatingip(
@ -67,12 +73,6 @@ class TrafficOperationsScenarioTest(test_base.LoadBalancerBaseTestWithCompute):
else:
cls.lb_vip_address = lb[const.VIP_ADDRESS]
waiters.wait_for_status(cls.mem_lb_client.show_loadbalancer,
cls.lb_id, const.PROVISIONING_STATUS,
const.ACTIVE,
CONF.load_balancer.lb_build_interval,
CONF.load_balancer.lb_build_timeout)
protocol = const.HTTP
lb_feature_enabled = CONF.loadbalancer_feature_enabled
if not lb_feature_enabled.l7_protocol_enabled: