Comment 10 for bug 1320617

Any update here? The DevStack patch seems to be abandoned.

In one of the comments, Sean Dague says "For instance, the orchestration image and timeout are coupled, and are set in the gate. The reason this is a timeout is that fedora is sometimes not booting at all in the gate."

Is the above still the case?

Meanwhile, I can confirm this same time-out issue reoccurring for "check-tempest-dsvm-full" job --

http://logs.openstack.org/90/102490/1/check/check-tempest-dsvm-full/b241a13/console.html#_2014-06-25_11_34_43_913

Contextual snippet:
--------------
[. . .]
2014-06-25 11:34:43.906 | Details: (ImagesOneServerTestJSON:tearDown) Server 6df01c6c-27a3-4e87-b25d-bc1d62dff5b9 failed to reach ACTIVE status and task state "None" within the required time (196 s). Current status: ACTIVE. Current task state: image_pending_upload.
2014-06-25 11:34:43.906 | 2014-06-25 11:16:00.362 21498 TRACE tempest.api.compute.base Traceback (most recent call last):
2014-06-25 11:34:43.906 | 2014-06-25 11:16:00.362 21498 TRACE tempest.api.compute.base File "tempest/api/compute/base.py", line 161, in server_check_teardown
2014-06-25 11:34:43.906 | 2014-06-25 11:16:00.362 21498 TRACE tempest.api.compute.base 'ACTIVE')
2014-06-25 11:34:43.906 | 2014-06-25 11:16:00.362 21498 TRACE tempest.api.compute.base File "tempest/services/compute/json/servers_client.py", line 173, in wait_for_server_status
2014-06-25 11:34:43.906 | 2014-06-25 11:16:00.362 21498 TRACE tempest.api.compute.base raise_on_error=raise_on_error)
2014-06-25 11:34:43.907 | 2014-06-25 11:16:00.362 21498 TRACE tempest.api.compute.base File "tempest/common/waiters.py", line 107, in wait_for_server_status
2014-06-25 11:34:43.907 | 2014-06-25 11:16:00.362 21498 TRACE tempest.api.compute.base raise exceptions.TimeoutException(message)
2014-06-25 11:34:43.907 | 2014-06-25 11:16:00.362 21498 TRACE tempest.api.compute.base TimeoutException: Request timed out
2014-06-25 11:34:43.907 | 2014-06-25 11:16:00.362 21498 TRACE tempest.api.compute.base Details: (ImagesOneServerTestJSON:tearDown) Server 6df01c6c-27a3-4e87-b25d-bc1d62dff5b9 failed to reach ACTIVE status and task state "None" within the required time (196 s). Current status: ACTIVE. Current task state: image_pending_upload.
2014-06-25 11:34:43.907 | 2014-06-25 11:16:00.362 21498 TRACE tempest.api.compute.base
[. . .]
--------------