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

Bug 1693295

Summary:	rpc.statd not started on builder204.aws.gluster.org
Product:	[Community] GlusterFS	Reporter:	Nithya Balachandran <nbalacha>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1	CC:	bugs, dkhandel, gluster-infra, mscherer
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-15 11:33:35 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 Nithya Balachandran 2019-03-27 13:26:11 UTC

Description of problem
https://build.gluster.org/job/centos7-regression/5244/ fails with:

11:59:01 mount.nfs: rpc.statd is not running but is required for remote locking.
11:59:01 mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
11:59:01 mount.nfs: an incorrect mount option was specified

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



How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 M. Scherer 2019-03-27 16:38:38 UTC

So, it fail because the network service didn't return correctly, but I can't find why this do happen. I may just reboot after the test is finished.

Comment 2 Deepshikha khandelwal 2019-04-15 11:33:35 UTC


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