Description of problem: The gluster peer probe command with invalid ips dont report that IP's can also be a valid in usage. [root@desktop8 /]# gluster peer status Number of Peers: 0 [root@desktop8 /]# ifconfig -a bash: ifconfig: command not found [root@desktop8 /]# ifconfig bash: ifconfig: command not found [root@desktop8 /]# gluster peer status Number of Peers: 0 [root@desktop8 /]# gluster peer probe server1 peer probe: failed: Probe returned with unknown errno 107 [root@desktop8 /]# gluster peer probe server223433 peer probe: failed: Probe returned with unknown errno 107 [root@desktop8 /]# gluster peer probe -1 -1 is an invalid address Usage: peer probe <HOSTNAME> ---- [root@desktop8 /] Version-Release number of selected component (if applicable): [root@desktop8 /]# rpm -qa | grep glusterfs glusterfs-3.5.0-0.5.beta3.fc20.x86_64 glusterfs-cli-3.5.0-0.5.beta3.fc20.x86_64 glusterfs-libs-3.5.0-0.5.beta3.fc20.x86_64 glusterfs-server-3.5.0-0.5.beta3.fc20.x86_64 glusterfs-fuse-3.5.0-0.5.beta3.fc20.x86_64 [root@desktop8 /]# How reproducible: Steps to Reproduce: 1. Install glusterfs of above version 2. Create bricks with XFS parttions and mount it 3. Issue gluster peer probe command with negative value Actual results: Usage: peer probe <HOSTNAME> Expected results: Usage: peer probe <HOSTNAME>/IP address Additional info:
BZ : 1247910 1242742
pre-release version is ambiguous and about to be removed as a choice. If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.