Bug 808655

Summary: [oVir][vdsm]storage create issue: LOCALFS, sometimes hang on storage.sdc.refreshStorage()
Product: [Retired] oVirt Reporter: wenchao xia <xiawenc>
Component: vdsmAssignee: wenchao xia <xiawenc>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: abaron, acathrow, amureini, bazulay, dyasny, iheim, ykaul
Target Milestone: ---   
Target Release: 3.3.4   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-12 09:37:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
test script to reproduce it, unzip it and run exe_test.sh
none
logs when the call hangs none

Description wenchao xia 2012-03-31 03:24:44 UTC
Created attachment 574124 [details]
test script to reproduce it, unzip it and run exe_test.sh

Description of problem:
    when createStorageDomain is called with a LOCALFS, sometimes it hang on at the step of refreshStorage() and never return.

Version-Release number of selected component (if applicable):
vdsm-cli-4.9.6-0.53.gitd4a0516.fc16.noarch
vdsm-4.9.6-0.53.gitd4a0516.fc16.x86_64
vdsm-python-4.9.6-0.53.gitd4a0516.fc16.noarch


How reproducible:
    often but not every time.

Steps to Reproduce:
1. restart vdsmd
2. connect storageServer with LOCALFS
3. create storageDomain
  
Actual results:
    step 3 sometime hang on

Expected results:
    it should return a result.

Additional info:
    There is somtimes another error tips "permission deny" in this case, I will fire it in another bug.

Comment 1 wenchao xia 2012-03-31 03:26:24 UTC
Created attachment 574125 [details]
logs when the call hangs

this is the log.

Comment 2 Itamar Heim 2013-03-12 09:37:33 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.