Bug 1278468

Summary:	rpcbind.socket not started after initial installation
Product:	Red Hat Enterprise Linux 7	Reporter:	Laurent Bigonville <bigon>
Component:	rpcbind	Assignee:	Steve Dickson <steved>
Status:	CLOSED DUPLICATE	QA Contact:	Filesystem QE <fs-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.1
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:	2016-04-09 14:42:26 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 Laurent Bigonville 2015-11-05 14:48:16 UTC

Description of problem:
When installing the rpcbind package, the rpcbind.socket unit is being enabled (via systemctl enable rpcbind.service call) but the socket itself is not started. That means that trying to mount a NFS 3 share just after that will fail because rpc-statd will fail to start because rpcbind is not running. After a reboot, the NFS share is mounted.

Version-Release number of selected component (if applicable):
rpcbind-0.2.0-26.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. install nfs-utils package
2. try to mount an nfs3 share
3. it fails to mount and rpc-statd is complaining that rpcbind is not running

Actual results:
NFS share not mounted just after installing nfs-utils/rpcbind package

Expected results:
NFS is mounted properly

Additional info:

Comment 2 Steve Dickson 2016-04-09 14:42:26 UTC


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