Bug 1091474

Summary:	pacemaker's nfsserver agent does not initialize rpc.statd for file locking
Product:	Red Hat Enterprise Linux 6	Reporter:	David Vossel <dvossel>
Component:	resource-agents	Assignee:	David Vossel <dvossel>
Status:	CLOSED DUPLICATE	QA Contact:	Cluster QE <mspqa-list>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	6.6	CC:	agk, cluster-maint, fdinitto
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-08 15:44:40 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:

Description David Vossel 2014-04-25 16:52:29 UTC

Description of problem:

Pacemaker's nfsserver resource-agent needs to initialize rpc.statd so NFSv3 file locking can take place properly.

How reproducible:
100%


Steps to Reproduce:

run this pacemaker scenario
https://github.com/davidvossel/phd/blob/master/scenarios/nfs-basic.scenario

on whatever node the nfsserver is active on, there will be no rpc.statd process.

Actual results:

no rpc.statd

Expected results:

rpc.statd

Comment 1 David Vossel 2014-05-08 15:44:40 UTC


*** This bug has been marked as a duplicate of bug 1091102 ***