This is upstream bug for https://bugs.launchpad.net/mos/+bug/1626505
In accordance to http://developer.openstack.org/api-ref-compute-v2.1.html#deleteFloatingIP , the normal response code here is '202', and it doesn't guarantee that operation is completed (all data about deleted IP are cleaned up) at the moment of response's sending. Since there is no waiter in the test, which checks the completion of floating IP's deletion process, it may lead to some race between 'floating IP delete' and 'nova show' operations and, as a result, test's failing.
To avoid it, we need to add such check to the 'delete floating IP' scenario's step.
Now this test passes against gates, but it fails against downstream Tempest CI jobs and against custom environments, and we don't have no guarantee that this race will never happen against gates.
The fix is proposed here: https:/