Bug 762288 (GLUSTER-556) - volume update doesn't preserve old ports
Summary: volume update doesn't preserve old ports
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-556
Product: GlusterSP
Classification: Retired
Component: core
Version: unspecified
Hardware: All
OS: Linux
low
high
Target Milestone: 3.0.5
Assignee: Balamurugan Arumugam
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-22 00:02 UTC by Amar Tumballi
Modified: 2013-12-19 00:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.