Race condition in test_servers_negative.py

I am seeing the following errors. They seem to be caused by the code creating a server, deleting it, and then doing a reboot/rebuild expecting the server to be deleted. But the code does wait for the server to be deleted. I added a call to wait_for_server_termination and the problem went away, but I am not sure what the point of creating and deleting the server is in this case. I am not sure why this has not been reported. I observe this with the current master for tempest/devstack but running devstack on a different server than tempest.

======================================================================
ERROR: Reboot a deleted server
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/cygdrive/c/source/tempest/tempest/tests/test_servers_negative.py", line 116, in test_reboot_deleted_server
    resp1, reboot_server = self.client.reboot(self.server_id, 'SOFT')
  File "/cygdrive/c/source/tempest/tempest/services/nova/json/servers_client.py", line 211, in reboot
    post_body, self.headers)
  File "/cygdrive/c/source/tempest/tempest/common/rest_client.py", line 152, in post
    return self.request('POST', url, headers, body)
  File "/cygdrive/c/source/tempest/tempest/common/rest_client.py", line 199, in request
    raise exceptions.Duplicate(resp_body)
Duplicate: An object with that identifier already exists
Details: An object with that identifier already exists
Details: {u'conflictingRequest': {u'message': u"Cannot 'reboot' while instance is in vm_state building", u'code': 409}}
-------------------- >> begin captured logging << --------------------
tempest.common.rest_client: ERROR: Request URL: http://172.18.0.156:8774/v2/fe4b597cb85140ada9ba0994012d4da9/servers/dfb02cb8-fd6c-4a73-b1fb-80f8b79c2b50/action
tempest.common.rest_client: ERROR: Request Body: {"reboot": {"type": "SOFT"}}
tempest.common.rest_client: ERROR: Response Headers: {'date': 'Wed, 30 May 2012 19:43:47 GMT', 'status': '409', 'content-length': '106', 'content-type': 'application/json; charset=UTF-8', 'x-compute-request-id': 'req-2a3fafce-93f7-452d-a824-162eaedb315f'}
tempest.common.rest_client: ERROR: Response Body: {u'conflictingRequest': {u'message': u"Cannot 'reboot' while instance is in vm_state building", u'code': 409}}
--------------------- >> end captured logging << ---------------------

======================================================================
ERROR: Rebuild a deleted server
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/cygdrive/c/source/tempest/tempest/tests/test_servers_negative.py", line 133, in test_rebuild_deleted_server
    self.image_ref_alt)
  File "/cygdrive/c/source/tempest/tempest/services/nova/json/servers_client.py", line 238, in rebuild
    self.headers)
  File "/cygdrive/c/source/tempest/tempest/common/rest_client.py", line 152, in post
    return self.request('POST', url, headers, body)
  File "/cygdrive/c/source/tempest/tempest/common/rest_client.py", line 199, in request
    raise exceptions.Duplicate(resp_body)
Duplicate: An object with that identifier already exists
Details: An object with that identifier already exists
Details: {u'conflictingRequest': {u'message': u"Cannot 'rebuild' while instance is in vm_state building", u'code': 409}}
-------------------- >> begin captured logging << --------------------
tempest.common.rest_client: ERROR: Request URL: http://172.18.0.156:8774/v2/fe4b597cb85140ada9ba0994012d4da9/servers/aaf3aa0a-2c66-4ea3-896f-5f2d23b38035/action
tempest.common.rest_client: ERROR: Request Body: {"rebuild": {"imageRef": "ee68ea71-d2c1-4ba8-b97c-3c9efd7023bc"}}
tempest.common.rest_client: ERROR: Response Headers: {'date': 'Wed, 30 May 2012 19:43:48 GMT', 'status': '409', 'content-length': '107', 'content-type': 'application/json; charset=UTF-8', 'x-compute-request-id': 'req-f0544e05-f0ad-41a0-93d6-cf8d7958202c'}
tempest.common.rest_client: ERROR: Response Body: {u'conflictingRequest': {u'message': u"Cannot 'rebuild' while instance is in vm_state building", u'code': 409}}
--------------------- >> end captured logging << ---------------------