Further fix to "test_list_shares_by_status"
We addressed some test flakiness issues in Ife979fd1c026a4c28caf72c012871761fe039988 We could improve this a bit more since there is more than one "migrating" state a share can get into; for example: "server_migrating". Change-Id: I2424ddf3e7ff9b9382288c3b73626dda81664eb7 Partial-Bug: #1821945 Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
This commit is contained in:
parent
89f32351db
commit
de1902786a
|
@ -168,7 +168,7 @@ class SharesListReadWriteTest(base.BaseTestCase):
|
|||
# between our 'list' and 'get' requests. Skip such case.
|
||||
# It occurs with concurrently running tests.
|
||||
continue
|
||||
if share_get['status'] == 'migrating':
|
||||
if 'migrating' in share_get['status']:
|
||||
# all bets are off, a fair chance share migration
|
||||
# started between the 'list' and 'get' requests. No need
|
||||
# to verify these shares.
|
||||
|
|
Loading…
Reference in New Issue