-
Bug
-
Resolution: Unresolved
-
Major
-
rhos-18.0.13
-
None
-
3
-
False
-
-
False
-
?
-
rhos-storage-manila
-
None
-
-
-
-
OSPRH Manila Sprint 9
-
1
-
Important
To Reproduce Steps to reproduce the behavior:
When one or more manila tests fail for any reason - for example, if a share fails to be deleted within a specified timeout, a number of unrelated tests also fail teardown. This is because they're all trying to cleanup failed resources. This would be okay if the tests shared the same project/credentials - however, the credential context is configurable, and re-attempting cleanup only works in a narrow set of use cases.
Expected behavior
- Cleanup failures must only fail the test that concerns the failed resource
Failure Log:
- testr results from a sample run are attached; sample log:
Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/manila_tempest_tests/tests/api/base.py", line 912, in clear_resources client.delete_share(res_id) File "/usr/lib/python3.9/site-packages/manila_tempest_tests/services/share/v2/json/shares_client.py", line 355, in delete_share resp, body = self.delete(uri, version=version) File "/usr/lib/python3.9/site-packages/manila_tempest_tests/services/share/v2/json/shares_client.py", line 85, in delete resp, body = super(SharesV2Client, self).delete(url, headers=headers, File "/usr/lib/python3.9/site-packages/tempest/lib/common/rest_client.py", line 359, in delete return self.request('DELETE', url, extra_headers, headers, body) File "/usr/lib/python3.9/site-packages/tempest/lib/common/rest_client.py", line 762, in request self._error_checker(resp, resp_body) File "/usr/lib/python3.9/site-packages/tempest/lib/common/rest_client.py", line 862, in _error_checker raise exceptions.Unauthorized(resp_body, resp=resp) tempest.lib.exceptions.Unauthorized: Unauthorized Details: {'code': 401, 'title': 'Unauthorized', 'message': 'The request you have made requires authentication.'}
Bug impact
- When CI fails a few tests, depending on when the failures occur, these unrelated test failures can clobber the results and make troubleshooting hard/annoying
Known workaround
- One can set `[share]/suppress_errors{_}in_cleanup=True` in tempest.conf to avoid seeing these failures, but, genuine cleanup test failures are also suppressed with this option
