yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #07089
[Bug 1258635] Re: Race with changing image status when snapshotting
** No longer affects: nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1258635
Title:
Race with changing image status when snapshotting
Status in Tempest:
Fix Released
Bug description:
{code}
19:18:16 ======================================================================
19:18:16 FAIL: setUpClass (tempest.api.compute.images.test_list_image_filters.ListImageFiltersTestJSON)
19:18:16 setUpClass (tempest.api.compute.images.test_list_image_filters.ListImageFiltersTestJSON)
19:18:16 ----------------------------------------------------------------------
19:18:16 _StringException: Traceback (most recent call last):
19:18:16 File "tempest/api/compute/images/test_list_image_filters.py", line 61, in setUpClass
19:18:16 resp, body = cls.create_image_from_server(cls.server1['id'])
19:18:16 File "tempest/api/compute/base.py", line 172, in create_image_from_server
19:18:16 server_id, name)
19:18:16 File "tempest/services/compute/json/images_client.py", line 49, in create_image
19:18:16 post_body, self.headers)
19:18:16 File "tempest/common/rest_client.py", line 302, in post
19:18:16 return self.request('POST', url, headers, body)
19:18:16 File "tempest/common/rest_client.py", line 436, in request
19:18:16 resp, resp_body)
19:18:16 File "tempest/common/rest_client.py", line 491, in _error_checker
19:18:16 raise exceptions.Conflict(resp_body)
19:18:16 Conflict: An object with that identifier already exists
19:18:16 Details: {u'conflictingRequest': {u'message': u"Cannot 'createImage' while instance is in task_state image_uploading", u'code': 409}}
{code}
This is a tempest bug - but the test creates a server, starts a
snapshot and then waits for the server to have the "ACTIVE" state.
There is waiting for the image to have finished uploading - but the
instance may not have been returned to the "ACTIVE" state immediately.
To manage notifications about this bug go to:
https://bugs.launchpad.net/tempest/+bug/1258635/+subscriptions
References