openstack
/
tempest
Code Issues Proposed changes

Wait for FIP status to get to DOWN in test_router_rescheduling 

If we don't wait until the port actually gets to DOWN in database, we
may proceed to scheduling the router again and check floating IP status,
expecting it to be ACTIVE, but then catch DOWN still in database because
the router was slow to process the unscheduling event.

Closes-Bug: #1644937
Change-Id: I0806ead789953a4ff879ef9e6e77e1c66e658316
This commit is contained in:
Ihar Hrachyshka 2016-11-13 11:54:54 +00:00
parent 274bb70c27
commit 3a0a0f7288
1 changed files with 0 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
tempest/scenario/test_network_basic_ops.py
View File

@ -748,7 +748,6 @@ class TestNetworkBasicOps(manager.NetworkScenarioTest):
self.check_public_network_connectivity( self.check_public_network_connectivity(
should_connect=False, should_connect=False,
msg='after router unscheduling', msg='after router unscheduling',
should_check_floating_ip_status=False
) )
# schedule resource to new agent # schedule resource to new agent