Comment 11 for bug 1531862

This occurred on a stable/kilo change too:

2016-03-23 22:32:37.809 | tempest.api.compute.servers.test_server_personality.ServerPersonalityTestJSON.test_rebuild_server_with_personality[id-128966d8-71fc-443c-8cab-08e24114ecc9]
2016-03-23 22:32:37.810 | -----------------------------------------------------------------------------------------------------------------------------------------------------------
2016-03-23 22:32:37.810 |
2016-03-23 22:32:37.810 | Captured traceback:
2016-03-23 22:32:37.810 | ~~~~~~~~~~~~~~~~~~~
2016-03-23 22:32:37.810 | Traceback (most recent call last):
2016-03-23 22:32:37.810 | File "tempest/api/compute/servers/test_server_personality.py", line 84, in test_rebuild_server_with_personality
2016-03-23 22:32:37.810 | waiters.wait_for_server_status(self.client, server_id, 'ACTIVE')
2016-03-23 22:32:37.811 | File "tempest/common/waiters.py", line 95, in wait_for_server_status
2016-03-23 22:32:37.811 | raise exceptions.TimeoutException(message)
2016-03-23 22:32:37.811 | tempest.exceptions.TimeoutException: Request timed out
2016-03-23 22:32:37.811 | Details: (ServerPersonalityTestJSON:test_rebuild_server_with_personality) Server d0060300-59b2-432f-89e9-3f56d45f0e50 failed to reach ACTIVE status and task state "None" within the required time (196 s). Current status: REBUILD. Current task state: rebuild_spawning.

http://logs.openstack.org/59/296659/2/check/gate-tempest-dsvm-neutron-linuxbridge/e51c86d/console.html