Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 918150

Summary: Deadlock in vdsm in attachStorageDomain
Product: Red Hat Enterprise Virtualization Manager Reporter: Katarzyna Jachim <kjachim>
Component: vdsmAssignee: Ayal Baron <abaron>
Status: CLOSED NOTABUG QA Contact: Katarzyna Jachim <kjachim>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.1.3CC: abaron, bazulay, hateya, iheim, jlibosva, lpeer, ncredi, ykaul
Target Milestone: ---Keywords: Regression, Reopened
Target Release: 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-08 20:38:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine log
none
/var/log/messages
none
sanlock.log
none
vdsm.log none

Description Katarzyna Jachim 2013-03-05 15:31:41 UTC 
Description of problem:
attachStorageDomain was called, it didn't return, so the engine called 
spmStop - in the same time test treated it as a correct behaviour and performed next action (activateStorageDomain)

there were several actions waiting on lock on Storage.54e52e78-ddb2-4dc4-a8c7-427d71be5f53


Version-Release number of selected component (if applicable): si27.3


How reproducible:
http://jenkins.qa.lab.tlv.redhat.com:8080/view/Storage/view/3.1/job/3.1-storage_sanity-iscsi-sdk/212/

https://tcms.engineering.redhat.com/plan/6458/rhevmstorage31-features-storage-sanity

Steps to Reproduce:
1. attach storage domain
2. try to activate it
  
Actual results:
ResourceTimeout in waititng for Storage.54e52e78-ddb2-4dc4-a8c7-427d71be5f53


Expected results:
No timeout

Additional info:
Comment 1 Katarzyna Jachim 2013-03-05 15:32:14 UTC 
Created attachment 705506 [details]
engine log
Comment 2 Katarzyna Jachim 2013-03-05 15:33:06 UTC 
Created attachment 705507 [details]
/var/log/messages
Comment 3 Katarzyna Jachim 2013-03-05 15:33:26 UTC 
Created attachment 705508 [details]
sanlock.log
Comment 4 Katarzyna Jachim 2013-03-05 15:33:47 UTC 
Created attachment 705509 [details]
vdsm.log
Comment 5 Ayal Baron 2013-03-05 21:20:24 UTC 
All attach operations in the provided vdsm log succeeded (longest one took 1.5m)

The resource timeout is on getStoragePoolInfo while spmStop is running:
MainThread::INFO::2013-03-05 00:30:55,279::logUtils::37::dispatcher::(wrapper) Run and protect: spmStop(spUUID='54e52e78-ddb2-4dc4-a8c7-427d71be5f53', options=None)

Engine did not initiate this spmStop, the test aparently did seeing as it is on the 'MainThread' and right before that there is a call to getConnectedStoragePoolsList which is not used by engine ever.

Please fix the test.