Bug 842750

Summary: [RHEV] Sanlock daemon can not be stopped running service sanlock stop because lockspaces still exist.
Product: Red Hat Enterprise Linux 6 Reporter: Leonid Natapov <lnatapov>
Component: sanlockAssignee: David Teigland <teigland>
Status: CLOSED NOTABUG QA Contact: Haim <hateya>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3CC: cluster-maint, fsimonce, hateya, yeylon
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-23 15:05:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 800588    
Attachments:
Description Flags
logs none

Description Leonid Natapov 2012-07-24 14:11:25 UTC
Created attachment 600036 [details]
logs

Sanlock daemon can not be stopped running 'service sanlock stop' because lockspaces still exist. We need to take care of the lockspaces and remove them  upon stopping sanlock daemon or forcibly shut down the sanlock daemon which will automatically remove any remaining lockspaces.


logs attached

Comment 2 David Teigland 2012-09-20 21:17:29 UTC
Can we close this bz?  I don't think this is a bug.

Comment 3 Leonid Natapov 2012-09-23 15:05:09 UTC
when there are no leases sanlock service can be successfully stopped running service sanlock stop.

when there are active leases service can not be stopped which is seems to be correct behavior.
closing this bz as not a bug.