Bug 1283527

Summary: [nfs service] "service nfs start" hang if rpcbind is stopped
Product: Red Hat Enterprise Linux 6 Reporter: Yongcheng Yang <yoyang>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED WONTFIX QA Contact: Filesystem QE <fs-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.7   
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: 2015-11-20 15:45:11 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 Yongcheng Yang 2015-11-19 08:45:43 UTC 
Description of problem:
If start nfs service while rpcbind is not started, it always hang about 20 minutes.

Version-Release number of selected component (if applicable):
nfs-utils-1.2.3-64.el6.x86_64

How reproducible:
100% easy

Steps to Reproduce:
1. service rpcbind stop; service nfs stop
2. service nfs start

Actual results:
[root@hp-dl160g8-01 ~]# service rpcbind stop; service nfs stop
Stopping rpcbind: [FAILED]
Shutting down NFS daemon: [FAILED]
Shutting down NFS mountd: [FAILED]
Shutting down NFS quotas: [FAILED]
[root@hp-dl160g8-01 ~]# time service nfs start
Starting NFS services:  [  OK  ]
Starting NFS quotas: Cannot register service: RPC: Unable to receive; errno = Connection refused
rpc.rquotad: unable to register (RQUOTAPROG, RQUOTAVERS, udp).
[FAILED]
Starting NFS mountd: [FAILED]
Starting NFS daemon: rpc.nfsd: writing fd to kernel failed: errno 110 (Connection timed out)
rpc.nfsd: unable to set any sockets for nfsd
[FAILED]

real	24m0.627s
user	0m0.176s
sys	0m0.290s
[root@hp-dl160g8-01 ~]# 

Expected results:
failed immediately

Additional info:
In RHEL7, starting nfs.service can bring rpcbind.service up:
[root@hp-dl385pg8-03 ~]# service rpcbind status 2>&1 | grep Active
   Active: inactive (dead) since Thu 2015-11-19 16:10:01 CST; 1min 1s ago
[root@hp-dl385pg8-03 ~]# service nfs status 2>&1 | grep Active
   Active: inactive (dead) since Thu 2015-11-19 16:09:22 CST; 1min 47s ago
[root@hp-dl385pg8-03 ~]# service nfs start
Redirecting to /bin/systemctl start  nfs.service
[root@hp-dl385pg8-03 ~]# service nfs status 2>&1 | grep Active
   Active: active (exited) since Thu 2015-11-19 16:11:17 CST; 2s ago
[root@hp-dl385pg8-03 ~]# service rpcbind status 2>&1 | grep Active
   Active: active (running) since Thu 2015-11-19 16:11:15 CST; 9s ago
[root@hp-dl385pg8-03 ~]# rpm -q nfs-utils
nfs-utils-1.3.0-0.21.el7.x86_64
[root@hp-dl385pg8-03 ~]#
Comment 2 Steve Dickson 2015-11-20 15:45:11 UTC 
(In reply to Yongcheng Yang from comment #0)
> Description of problem:
> If start nfs service while rpcbind is not started, it always hang about 20
> minutes.
> 
> Version-Release number of selected component (if applicable):
> nfs-utils-1.2.3-64.el6.x86_64
> 
> How reproducible:
> 100% easy
> 
> Steps to Reproduce:
> 1. service rpcbind stop; service nfs stop
> 2. service nfs start
I do not see how a customer would ever run into
something this... There is simply no reason 
to do something like this.

So with all due respect, I really don't want to
spend any cycles on the "Don't do that" type of
problem.