Red Hat Bugzilla – Bug 817648
cli: peer probe returns value 0 even in case of error
Last modified: 2014-04-17 07:38:46 EDT
[root@gqac026 ~]# gluster peer probe 10.16.157.781
Usage: peer probe <HOSTNAME>
[root@gqac026 ~]# echo $?
In the above case, the peer probe has failed due to wrong ip address. In such cases return a value other than 0. This helps while scripting these commands.
Fixed by commit ada4ab0 (cli: Fix error output for peer probe on address validation failure)
[root@dhcp159-156 tmp]# gluster peer probe 10.16.157.781
[root@dhcp159-156 tmp]# echo $?
This is a regression. No ipv4 validation done. I expect to see a message saying ip address is wrong and fail with a non-zero error code.
(In reply to comment #2)
> This is a regression. No ipv4 validation done. I expect to see a message
> saying ip address is wrong and fail with a non-zero error code.
Should we rather open different bug for missing validation? or you are saying earlier there was validation, and now we removed it?
This is the error on latest master.
[root@supernova ~]# gluster peer probe 10.16.157.781
peer probe: failed: Probe returned with unknown errno 107
[root@supernova ~]# echo $?
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.5.0, please reopen this bug report.
glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.