Closed
Description
Description of problem:
When a "peer probe" command is executed with a bogus name (i.e. it won't be resolved by local /etc/hosts, DNS or any other name service), gluster may crash.
The exact command to reproduce the issue:
Just run gluster peer probe non-existent-name. However this has been detected as part of the work related to #3469 because one existing test was consistently failing on my setup, while it seems to be working fine in the automated regression test run (it's a timing issue).