Volume test_detach failed to reach in-use status within the required time (400 s).

[Attila Fazekas]

http://logs.openstack.org/78/45578/12/gate/gate-tempest-devstack-vm-full/70cd7a5/

2013-09-26 02:29:24.949 | Traceback (most recent call last):
2013-09-26 02:29:24.949 | File "tempest/api/compute/servers/test_server_rescue.py", line 180, in test_rescued_vm_detach_volume
2013-09-26 02:29:24.949 | self.volume_to_detach['id'], 'in-use')
2013-09-26 02:29:24.949 | File "tempest/services/compute/json/volumes_extensions_client.py", line 104, in wait_for_volume_status
2013-09-26 02:29:24.949 | raise exceptions.TimeoutException(message)
2013-09-26 02:29:24.949 | TimeoutException: Request timed out
2013-09-26 02:29:24.950 | Details: Volume test_detach failed to reach in-use status within the required time (400 s).

Related exception in the n-cpu log: http://logs.openstack.org/78/45578/12/gate/gate-tempest-devstack-vm-full/70cd7a5/logs/screen-n-cpu.txt.gz#_2013-09-26_02_15_37_212

[Matthew Treinish (treinish)]

I think that this is a dup of bug 1226337 because it has the same exception in nova. Yes, it's failing on a different tempest test but it looks like the underlying failure is the same. Because, we're doing a volume attach separately in this test it's a timeout but in 1226337 it's a during boot from volume the server goes into an error state.

[David Kranz (david-kranz)]

This just happened with http://logs.openstack.org/08/47508/6/gate/gate-tempest-devstack-vm-full/90a72c3/console.html
even though the bug this is a duplicate of has been Fix Released.