I cannot spot the clear issue from nova or cinder flow of failed volume. Issue happening during the test cleanup when attached volume from rescued server is requested for detach
tempest log:
Test performed all operation till unrescue the server and server became Active with same attachment it had before rescue.
Now cleanup started and test requested the volume detach. It waiting for volume status in 'detaching' and after lot of time volume
status changed to 'in-use'
In n-cpu log i am seeing another test trying to detach volume from mountpoint /dev/vdb and failing but it is different server so not sure
if that is any issue?
Another test req-4542a8aa-6deb-434c-9905-99d3eb44f029 tempest-AttachVolumeMultiAttachTest-1857486939
I cannot spot the clear issue from nova or cinder flow of failed volume. Issue happening during the test cleanup when attached volume from rescued server is requested for detach
tempest log:
Test performed all operation till unrescue the server and server became Active with same attachment it had before rescue.
- https:/ /zuul.opendev. org/t/openstack /build/ 9290c83e18a741a 5bdab4e28de5eed b7/log/ job-output. txt#28627
Now cleanup started and test requested the volume detach. It waiting for volume status in 'detaching' and after lot of time volume
status changed to 'in-use'
- https:/ /zuul.opendev. org/t/openstack /build/ 9290c83e18a741a 5bdab4e28de5eed b7/log/ job-output. txt#29157- 29168
Trying to find the flow of same volume in cinder log:
volume is created fine:
- https:/ /zuul.opendev. org/t/openstack /build/ 9290c83e18a741a 5bdab4e28de5eed b7/log/ controller/ logs/screen- c-vol.txt# 8021
iscsi target is set correctly
- https:/ /zuul.opendev. org/t/openstack /build/ 9290c83e18a741a 5bdab4e28de5eed b7/log/ controller/ logs/screen- c-vol.txt# 8150
attachment is updated fine /zuul.opendev. org/t/openstack /build/ 9290c83e18a741a 5bdab4e28de5eed b7/log/ controller/ logs/screen- c-vol.txt# 8268
- https:/
Detach request
n-api log: req-baec6727- 9502-40d0- b4c4-f4e0e56973 e0 /zuul.opendev. org/t/openstack /build/ 9290c83e18a741a 5bdab4e28de5eed b7/log/ controller/ logs/screen- n-api.txt# 32946
- https:/
-c-api /zuul.opendev. org/t/openstack /build/ 9290c83e18a741a 5bdab4e28de5eed b7/log/ controller/ logs/screen- c-api.txt# 22785
- https:/
detaching of volume is completed /zuul.opendev. org/t/openstack /build/ 9290c83e18a741a 5bdab4e28de5eed b7/log/ controller/ logs/screen- c-api.txt# 22798
- https:/
removed the iscsi target /zuul.opendev. org/t/openstack /build/ 9290c83e18a741a 5bdab4e28de5eed b7/log/ controller/ logs/screen- c-vol.txt# 11495
- https:/
In n-cpu log i am seeing another test trying to detach volume from mountpoint /dev/vdb and failing but it is different server so not sure
if that is any issue?
Another test req-4542a8aa- 6deb-434c- 9905-99d3eb44f0 29 tempest- AttachVolumeMul tiAttachTest- 1857486939
- https:/ /zuul.opendev. org/t/openstack /build/ 9290c83e18a741a 5bdab4e28de5eed b7/log/ controller/ logs/screen- n-cpu.txt# 49802
failing tests req-baec6727- 9502-40d0- b4c4-f4e0e56973 e0 tempest- ServerStableDev iceRescueTest- 543821642 /zuul.opendev. org/t/openstack /build/ 9290c83e18a741a 5bdab4e28de5eed b7/log/ controller/ logs/screen- n-cpu.txt# 49785
- https:/