tempest

ContainerSyncTest calls delete_containers after clearing creds

Bug #1437000 reported by melanie witt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Invalid
Undecided
Unassigned

Bug Description

ContainerSyncTest calls delete_containers in the resource_cleanup function, which is called after clear_isolated_creds.

I think this is a race that can result in the following failure if the credentials are gone by the time the containers are attempted to be deleted:

[-] teardown of resources failed: Unauthorized
Details: <html><h1>Unauthorized</h1><p>This server could not verify that you are authorized to access the document you requested.</p></html>
2015-03-17 22:39:28.126 21149 TRACE tempest.test Traceback (most recent call last):
2015-03-17 22:39:28.126 21149 TRACE tempest.test File "tempest/test.py", line 288, in tearDownClass
2015-03-17 22:39:28.126 21149 TRACE tempest.test teardown()
2015-03-17 22:39:28.126 21149 TRACE tempest.test File "tempest/api/object_storage/test_container_sync.py", line 81, in resource_cleanup
2015-03-17 22:39:28.126 21149 TRACE tempest.test cls.delete_containers(cls.containers, client[0], client[1])
2015-03-17 22:39:28.126 21149 TRACE tempest.test File "tempest/api/object_storage/base.py", line 95, in delete_containers
2015-03-17 22:39:28.126 21149 TRACE tempest.test objlist = container_client.list_all_container_objects(cont)
2015-03-17 22:39:28.126 21149 TRACE tempest.test File "tempest/services/object_storage/container_client.py", line 118, in list_all_container_objects
2015-03-17 22:39:28.126 21149 TRACE tempest.test params={'limit': limit, 'format': 'json'})
2015-03-17 22:39:28.126 21149 TRACE tempest.test File "tempest/services/object_storage/container_client.py", line 180, in list_container_contents
2015-03-17 22:39:28.126 21149 TRACE tempest.test resp, body = self.get(url, headers={})
2015-03-17 22:39:28.126 21149 TRACE tempest.test File "/opt/stack/new/tempest/.tox/all/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py", line 172, in get
2015-03-17 22:39:28.126 21149 TRACE tempest.test return self.request('GET', url, extra_headers, headers)
2015-03-17 22:39:28.126 21149 TRACE tempest.test File "/opt/stack/new/tempest/.tox/all/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py", line 388, in request
2015-03-17 22:39:28.126 21149 TRACE tempest.test resp, resp_body)
2015-03-17 22:39:28.126 21149 TRACE tempest.test File "/opt/stack/new/tempest/.tox/all/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py", line 428, in _error_checker
2015-03-17 22:39:28.126 21149 TRACE tempest.test raise exceptions.Unauthorized(resp_body)
2015-03-17 22:39:28.126 21149 TRACE tempest.test Unauthorized: Unauthorized
2015-03-17 22:39:28.126 21149 TRACE tempest.test Details: <html><h1>Unauthorized</h1><p>This server could not verify that you are authorized to access the document you requested.</p></html>
2015-03-17 22:39:28.126 21149 TRACE tempest.test

Revision history for this message
melanie witt (melwitt) wrote :

Chatting in #openstack-qa it was noted that this test test_container_synchronization has @test.attr(type='slow') and the failure happened because the test timeout was hit.

Also, credentials are cleared AFTER resource_cleanup, so there is no race here. The teardown items are LIFO.

Changed in tempest:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.