Bug 783775

Summary: [ovirt] [vdsm] resource locking problem: vms are stuck on wait-for-lunch
Product: [Retired] oVirt Reporter: Haim <hateya>
Component: vdsmAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: abaron, acathrow, bazulay, hateya, iheim, mgoldboi, yeylon, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-12 08:55:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
logs none

Description Haim 2012-01-22 13:46:44 UTC 
Description of problem:

- using script, run over a bunch of vms (50), start vm's that are down, stop vm's that are up.
- 5 out of 50 vms are stuck on wait for lunch for good.

attached file with all required information:
1. log snippted with some grep showing where the problem might be
2. output of vdsClient 

[root@rhev-a24c-03 ~]# vdsClient -s 0 list table | grep Wait
323d3dd5-cc6b-4e31-8210-f55c7fb96ca8      0  myVm7                WaitForLaunch                            
396a4645-9b9d-4a4c-b3a9-eed0320fb8a3      0  myVm9                WaitForLaunch                            
0a6ee3a6-cd6b-49d0-ad60-5a5a1d0f16be      0  myVm6                WaitForLaunch                            
9365c81d-c075-47c7-ae58-2f66cff1ae05      0  myVm8                WaitForLaunch                            
75f8b814-8a85-4bb0-a428-523e0ec6875c      0  myVm0                
WaitForLaunch
Comment 1 Haim 2012-01-22 13:51:17 UTC 
Created attachment 556785 [details]
logs

git commit 5a0b2c912fb0ea5a305f191e9b558385ef249caa
Comment 2 Itamar Heim 2013-03-12 08:55:48 UTC 
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.