During cloning of VM with multiple big disks from snapshot we got errors in WebUI:
2/10/22 4:00:38 PM: VDSM command CopyImageVDS failed: Resource timeout: ()
2/10/22 4:00:38 PM: Failed to create VM foreman-test
2/10/22 4:00:47 PM: VDSM node-ib2-bl8.vdi.in.cz.net command HSMGetAllTasksStatusesVDS failed: value=f269c6d6-5009-4ef5-b7bb-59220843c17a abortedcode=411
The second problem is that failed task still looks as running in webUI.
We tried to run "Cleanup Finished Tasks" and next error occured in WebUI:
2/10/22 7:14:02 PM: VDSM node-ib2-bl8.vdi.in.cz.net command HSMGetAllTasksStatusesVDS failed: value=f269c6d6-5009-4ef5-b7bb-59220843c17a abortedcode=411
Tasks looks cleaned, but failed tasks still looks running in webUI:
vdsm-client Host getAllTasksStatuses
{}
Cloned VM disks images are still locked.
Version-Release number of selected component (if applicable):
4.4.10.6-1.el8
During cloning of VM with multiple big disks from snapshot we got errors in WebUI: 2/10/22 4:00:38 PM: VDSM command CopyImageVDS failed: Resource timeout: () 2/10/22 4:00:38 PM: Failed to create VM foreman-test 2/10/22 4:00:47 PM: VDSM node-ib2-bl8.vdi.in.cz.net command HSMGetAllTasksStatusesVDS failed: value=f269c6d6-5009-4ef5-b7bb-59220843c17a abortedcode=411
The second problem is that failed task still looks as running in webUI.
vdsm-client Host getAllTasksStatuses
{ "674e85fa-992f-45f5-90de-958740541b88": { "code": 411, "message": "value=674e85fa-992f-45f5-90de-958740541b88 abortedcode=411", "taskID": "674e85fa-992f-45f5-90de-958740541b88", "taskResult": "cleanSuccess", "taskState": "finished" }, "7e004f6b-5172-42f5-b714-1a70ca2f42f6": { "code": 411, "message": "value=7e004f6b-5172-42f5-b714-1a70ca2f42f6 abortedcode=411", "taskID": "7e004f6b-5172-42f5-b714-1a70ca2f42f6", "taskResult": "cleanSuccess", "taskState": "finished" }, "c3b0a3e2-94d2-49a7-92b8-3f0e49c18bc3": { "code": 411, "message": "value=c3b0a3e2-94d2-49a7-92b8-3f0e49c18bc3 abortedcode=411", "taskID": "c3b0a3e2-94d2-49a7-92b8-3f0e49c18bc3", "taskResult": "cleanSuccess", "taskState": "finished" }, "f269c6d6-5009-4ef5-b7bb-59220843c17a": { "code": 411, "message": "value=f269c6d6-5009-4ef5-b7bb-59220843c17a abortedcode=411", "taskID": "f269c6d6-5009-4ef5-b7bb-59220843c17a", "taskResult": "cleanSuccess", "taskState": "finished" } }
We tried to run "Cleanup Finished Tasks" and next error occured in WebUI: 2/10/22 7:14:02 PM: VDSM node-ib2-bl8.vdi.in.cz.net command HSMGetAllTasksStatusesVDS failed: value=f269c6d6-5009-4ef5-b7bb-59220843c17a abortedcode=411
Tasks looks cleaned, but failed tasks still looks running in webUI:
vdsm-client Host getAllTasksStatuses
{}
Cloned VM disks images are still locked.
Version-Release number of selected component (if applicable): 4.4.10.6-1.el8
Original bug: https://bugzilla.redhat.com/2053290