Bug 762806 (GLUSTER-1074) - port related issues in 'gluster probe' command
Summary: port related issues in 'gluster probe' command
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1074
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-14 19:30 UTC by Amar Tumballi
Modified: 2015-12-01 16:45 UTC (History)
2 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-07-14 19:30:52 UTC 
currently the way we use to set the remote port is not scalable, and hence we need more cleaner approach to set the remote-port while doing 'gluster probe'.
Comment 1 Amar Tumballi 2010-07-19 07:05:40 UTC 
as per the specs.. we don't need option of 'port' in 'gluster probe <hostname>', I will keep this open till we fix current outstanding bugs in 'gluster' command.
Comment 2 Anand Avati 2010-07-21 00:44:21 UTC 
PATCH: http://patches.gluster.com/patch/3793 in master (add port as an optional argument to 'probe' command)
Note You need to log in before you can comment on or make changes to this bug.