tree f0fc012f451950c35e0f5fe85676771c08f7667f
parent 274bb70c27cd69dc6ad48195a23e2fe1536b4cfd
author Ihar Hrachyshka <ihrachys@redhat.com> 1479038094 +0000
committer Ihar Hrachyshka <ihrachys@redhat.com> 1479038331 +0000

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