Bug 783775 - [ovirt] [vdsm] resource locking problem: vms are stuck on wait-for-lunch
Summary: [ovirt] [vdsm] resource locking problem: vms are stuck on wait-for-lunch
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Michal Skrivanek
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-22 13:46 UTC by Haim
Modified: 2014-01-13 00:50 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-12 08:55:48 UTC
oVirt Team: ---

Attachments (Terms of Use)
logs (4.83 MB, application/x-tar)
2012-01-22 13:51 UTC, Haim 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.