| commit | e4ee76252fd3e81bd0b325543b20a4024f74f7b1 | [log] [tgz] |
|---|---|---|
| author | Artom Lifshitz <alifshit@redhat.com> | Tue Jul 12 12:03:15 2022 -0400 |
| committer | Martin Kopec <mkopec@redhat.com> | Wed Jul 27 18:52:32 2022 +0000 |
| tree | 85b3f465927a3afbaa5f950cc10d38368397e1b4 | |
| parent | 4e994020d06834bd5494601470bc5ac08d74a3aa [diff] |
Clean up scenario floating IP waiting In changes I0f7e1c9096dc1903903fb31c5e854f07800efbfd and I05e079237aec332925a88476e45071b34dc722c6 we started waiting for a floating IP to appear in the Nova 'show server details' API before continuing with the test. This left some useless test code left over that needlessly asserted that the floating IP was showing up (or had disappeared, in the case of disassociation) from the Nova 'show server details' API after the waiter had already checked the same thing. This patch cleans this up. Change-Id: I692402cf0d831c524ca5f49daf4aa9b0d19d41b5