ServerRescueNegativeTestJSON:tearDownClass Failed to delete volume XXX within the required time (196 s).

Bug #1382581 reported by Mate Lakat
This bug report is a duplicate of:  Bug #1373513: Lvm hang during tempest tests. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
New
Undecided
Unassigned
OpenStack Compute (nova)
New
Undecided
Unassigned
tempest
New
Undecided
Unassigned

Bug Description

See also http://logs.openstack.org/11/129211/1/check/check-tempest-dsvm-postgres-full/22c6043/console.html

==============================
Failed 1 tests - output below:
==============================

tearDownClass (tempest.api.compute.servers.test_server_rescue_negative.ServerRescueNegativeTestJSON)
----------------------------------------------------------------------------------------------------

Captured traceback:
~~~~~~~~~~~~~~~~~~~
    Traceback (most recent call last):
      File "tempest/test.py", line 293, in tearDownClass
        cls.resource_cleanup()
      File "tempest/api/compute/servers/test_server_rescue_negative.py", line 60, in resource_cleanup
        cls.delete_volume(cls.volume['id'])
      File "tempest/api/compute/base.py", line 355, in delete_volume
        cls._delete_volume(cls.volumes_extensions_client, volume_id)
      File "tempest/api/compute/base.py", line 295, in _delete_volume
        volumes_client.wait_for_resource_deletion(volume_id)
      File "tempest/common/rest_client.py", line 578, in wait_for_resource_deletion
        raise exceptions.TimeoutException(message)
    TimeoutException: Request timed out
    Details: (ServerRescueNegativeTestJSON:tearDownClass) Failed to delete volume 15641df8-eb69-4bf4-a67b-159e922f7739 within the required time (196 s).

Revision history for this message
Clark Boylan (cboylan) wrote :

Removed openstack-infra and added cinder, nova, tempest because this looks like a legit failure to remove a volume from an instance.

no longer affects: openstack-ci
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.