Bug 762806 (GLUSTER-1074)

Summary: port related issues in 'gluster probe' command
Product: [Community] GlusterFS Reporter: Amar Tumballi <amarts>
Component: coreAssignee: Amar Tumballi <amarts>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: mainlineCC: gluster-bugs, vraman
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 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)