| *** ykarel|away is now known as ykarel | 05:01 | |
| *** pojadhav|out is now known as pojadhav | 06:00 | |
| *** jpena|off is now known as jpena | 07:35 | |
| *** bhagyashris is now known as bhagyashris|ruck | 07:57 | |
| *** arxcruz|rover is now known as arxcruz | 08:10 | |
| opendevreview | Attila Fazekas proposed openstack/tempest-stress master: Unit test logging https://review.opendev.org/c/openstack/tempest-stress/+/856688 | 09:21 |
|---|---|---|
| afazekas | https://review.opendev.org/c/openstack/tempest-stress/+/855612 | 09:42 |
| *** pojadhav is now known as pojadhav|sick | 11:05 | |
| *** abishop_ is now known as abishop | 15:12 | |
| *** jpena is now known as jpena|off | 16:35 | |
| abdi | No sure if this is the right forum for this question. Please direct me to the right place if not. | 19:42 |
| abdi | I have a tempest testtempest.api.compute.admin.test_volume_swap.TestMultiAttachVolumeSwap.test_volume_swap_with_multiattach that fails fairly consistently but once in a while passes. | 19:43 |
| abdi | From tempest.log I have narrowed down the issue to a volume detach taking a long time. expl: tempest.common.waiters [-] volume 52fd7229-2513-4be9-ba0d-a3d21387a44d reached in-use after waiting for 1042.730467 seconds. | 19:44 |
| abdi | Does anyone know how I can further dig into the detach operation and understand where exactly it is spending time? | 19:45 |
| abdi | By the way, my tempest tests are to validate a cinder driver. Thanks ahead. | 19:46 |
| clarkb | abdi: I woul dlook in your cinder logs and trace the detach through the cinder service to find where the time is being spent | 20:44 |
| abdi | @clarkb Thank you for the suggestion. Specifically, you mean the cinder-volume.log correct? | 20:48 |
| clarkb | abdi: yes and the cinder api log too probably | 20:48 |
| abdi | clarb: Will do. | 20:50 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!