Bug 1693295 - rpc.statd not started on builder204.aws.gluster.org
Summary: rpc.statd not started on builder204.aws.gluster.org
Keywords:
Status: CLOSED DUPLICATE of bug 1691789
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: 4.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-27 13:26 UTC by Nithya Balachandran
Modified: 2019-04-15 11:33 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-04-15 11:33:35 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.