Tempest test case tempest.api.volume.test_volumes_actions.VolumesV2ActionsTest fails with NetAPP + NFS setup in Juno based
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Setup:
June based installation with NetAPP NFS as storage backend. Glance images are stored in Swift.
Issue:
Tempest test case tempest.
Traceback (most recent call last):
File "/opt/stack/
return f(self, *func_args, **func_kwargs)
File "/opt/stack/
self.
File "/opt/stack/
raise exceptions.
TimeoutException: Request timed out
Details: (VolumesV2Actio
It seems the portion of cinder volume create and uploads to glance image is failing. glance image-list shows the newly created image in 'saving' status
for quite a long time [more than 30 minutes]. But once the tempest test fails, the new image is seems as active in glance.
A manual testing [volume creation and uploading the volume to glance] is pretty fast compared to tempest testing.
Is there a timeout value which i can increase for tempest testing? Or is this an issue with tempest test method?
The cinder-volume log shows the following snippet for the volume UUID 40fdecd0-
The cinder-volume log shows the following snippet for the volume UUID 40fdecd0- 3de3-43b7- 8a16-01a9f4b1c5 0e: