Comment 6 for bug 1273908

Revision history for this message
Zhikun Liu (zhikunliu) wrote :

Got the same problem: http://logs.openstack.org/74/96674/2/check/check-tempest-dsvm-full/9384da3/console.html.gz

2014-05-30 10:37:01.022 | {0} tempest.api.compute.v3.servers.test_server_rescue_negative.ServerRescueNegativeV3Test.test_rescued_vm_detach_volume [197.475501s] ... FAILED
2014-05-30 10:37:01.022 |
2014-05-30 10:37:01.022 | Captured traceback:
2014-05-30 10:37:01.022 | ~~~~~~~~~~~~~~~~~~~
2014-05-30 10:37:01.022 | Traceback (most recent call last):
2014-05-30 10:37:01.022 | File "tempest/api/compute/v3/servers/test_server_rescue_negative.py", line 127, in test_rescued_vm_detach_volume
2014-05-30 10:37:01.022 | self.volumes_client.wait_for_volume_status(self.volume['id'], 'in-use')
2014-05-30 10:37:01.022 | File "tempest/services/volume/json/volumes_client.py", line 169, in wait_for_volume_status
2014-05-30 10:37:01.022 | raise exceptions.TimeoutException(message)
2014-05-30 10:37:01.022 | TimeoutException: Request timed out
2014-05-30 10:37:01.022 | Details: Volume 2483e089-ebe1-45ee-bcf8-9c9aa7832d88 failed to reach in-use status within the required time (196 s).