Bug 762288 (GLUSTER-556)

Summary:	volume update doesn't preserve old ports
Product:	[Retired] GlusterSP	Reporter:	Amar Tumballi <amarts>
Component:	core	Assignee:	Balamurugan Arumugam <bala>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	low
Version:	unspecified	CC:	fharshav, pavan, platform, vraman, webteam
Target Milestone:	3.0.5
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 Amar Tumballi 2010-01-22 00:02:47 UTC

i stop the volume.. i goto volume properties by clicking on the volume.. now enable the NFS on volume (which was not there earlier).. now the volume files get new port.. 

not so desired behavior.. because even if you stop the volume on server, clients may be running, and when it comes back again, it will fail because they are trying to connect to old port..

-Amar

Comment 1 Amar Tumballi 2010-09-14 06:58:08 UTC

with 3.1, gluster platform uses 'gluster' cli to create volumes, hence that takes care of these issues.