Bug 1457617

Summary:	glusterd fails to start due to dependency issues
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	krishnaram Karthick <kramdoss>
Component:	rhgs-server-container	Assignee:	Humble Chirammal <hchiramm>
Status:	CLOSED DUPLICATE	QA Contact:	krishnaram Karthick <kramdoss>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	cns-3.6	CC:	hchiramm, kramdoss, madam, pprakash, rhs-bugs, sankarshan
Target Milestone:	---
Target Release:	CNS 3.6
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:	2017-06-22 11:24:29 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:
Bug Depends On:
Bug Blocks:	1445448

Description krishnaram Karthick 2017-06-01 04:04:32 UTC

Description of problem:

glusterd fails to start with rhgs container image 'rhgs-server-rhel7:3.3.0-2' due to dependency issue and as a result cns-deploy fails.

This is what I see from journal logs.

Jun 01 03:57:30 dhcp47-59.lab.eng.blr.redhat.com systemd[1]: Starting RPCbind Server Activation Socket.
-- Subject: Unit rpcbind.socket has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit rpcbind.socket has begun starting up.
Jun 01 03:57:48 dhcp47-59.lab.eng.blr.redhat.com systemd[1]: rpcbind.socket failed to listen on sockets: Address already in use
Jun 01 03:57:48 dhcp47-59.lab.eng.blr.redhat.com systemd[1]: Failed to listen on RPCbind Server Activation Socket.
-- Subject: Unit rpcbind.socket has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit rpcbind.socket has failed.
-- 
-- The result is failed.
Jun 01 03:57:48 dhcp47-59.lab.eng.blr.redhat.com systemd[1]: Dependency failed for RPC bind service.
-- Subject: Unit rpcbind.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit rpcbind.service has failed.
-- 
-- The result is dependency.
Jun 01 03:57:48 dhcp47-59.lab.eng.blr.redhat.com systemd[1]: Dependency failed for GlusterFS, a clustered file-system server.
-- Subject: Unit glusterd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit glusterd.service has failed.
-- 
-- The result is dependency.
Jun 01 03:57:48 dhcp47-59.lab.eng.blr.redhat.com systemd[1]: Job glusterd.service/start failed with result 'dependency'.
Jun 01 03:57:48 dhcp47-59.lab.eng.blr.redhat.com systemd[1]: Job rpcbind.service/start failed with result 'dependency'.

Version-Release number of selected component (if applicable):
rpm -qa | grep 'cns'
cns-deploy-5.0.0-1.el7rhgs.x86_64
[root@dhcp46-161 ~]# rpm -qa | grep 'heketi'
heketi-client-5.0.0-1.el7rhgs.x86_64

oc version
oc v3.6.85
kubernetes v1.6.1+5115d708d7
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://dhcp46-161.lab.eng.blr.redhat.com:8443
openshift v3.6.85
kubernetes v1.6.1+5115d708d7


How reproducible:
Always

Steps to Reproduce:
1. run cns-deploy with the above mentioned builds on openshift 3.6

Actual results:
glusterd fails to start 

Expected results:
glusterd should be started successfully

Additional info:

Comment 3 Humble Chirammal 2017-06-01 04:23:10 UTC

Karthick , Can you stop rpcbind in the host and try again?

Comment 4 krishnaram Karthick 2017-06-01 04:33:42 UTC

(In reply to Humble Chirammal from comment #3)
> Karthick , Can you stop rpcbind in the host and try again?

Yes, that helped.

stopping 'rpcbind' and 'rpcbind.socket' helped in starting glusterd service.  Thanks.

Comment 8 Humble Chirammal 2017-06-22 11:24:29 UTC


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