Bug 762325 (GLUSTER-593)

Summary:	Not able to mount after update
Product:	[Retired] GlusterSP	Reporter:	Raghavendra Bhat <rabhat>
Component:	core	Assignee:	Balamurugan Arumugam <bala>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	low
Version:	unspecified	CC:	platform, webteam
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Raghavendra Bhat 2010-02-04 14:29:52 UTC

After update was clicking under volume parameters the glusterfs client cannot be mounted. It gives transport end-point not connected.

After checking the volume files on the server it was seen that glusterfs server daemon was not restarted at all after the volume updation and it was running in an old port. 

Volume files were reflecting 10004 but the netstat -ntlp yielded that glusterfs daemon was running at 10002 port.

Comment 1 Balamurugan Arumugam 2010-02-07 19:47:58 UTC

This is required behavior that remounting should be done at client side after restarting volume.