While working on bug #1225462 on a host with 2 nics on 2 different networks I probed hosts on 192.168.1. network while the local glusterd chose the 10.0.0. address. trying to probe locally the nic on 192.168.1. was not useful since if you probe an additional interface for a host from itself, it will be ignored. A solution was to go on the other hosts and probe the initial host on 192.168.1. It would be nice to drop the need to go to the other host and peer probe the initial host since it already knows that additional hosts are reachable and it already knows by route which network should be used for reaching the other hosts.
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.