Comment 2 for bug 1882521
Revision history for this message
| Ghanshyam Mann (ghanshyammann) wrote Re: Failing device detachments on Focal | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
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:/
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:/
Trying to find the flow of same volume in cinder log:
volume is created fine:
- https:/
iscsi target is set correctly
- https:/
attachment is updated fine
- https:/
Detach request
n-api log: req-baec6727-
- https:/
-c-api
- https:/
detaching of volume is completed
- https:/
removed the iscsi target
- 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-
- https:/
failing tests req-baec6727-
- https:/