Bug 1105337

REVIEW: http://review.gluster.org/7997 (geo-rep/gverify: Never use ping to check for host reachability) posted (#2) for review on master by Harshavardhana (harsha)

REVIEW: http://review.gluster.org/7997 (geo-rep/gverify: Never use ping to check for host reachability) posted (#3) for review on master by Harshavardhana (harsha)

REVIEW: http://review.gluster.org/7997 (geo-rep/gverify: Never use ping to check for host reachability) posted (#4) for review on master by Harshavardhana (harsha)

REVIEW: http://review.gluster.org/7997 (geo-rep/gverify: Never use ping to check for host reachability) posted (#5) for review on master by Harshavardhana (harsha)

REVIEW: http://review.gluster.org/7997 (geo-rep/gverify: Never use ping to check for host reachability) posted (#6) for review on master by Harshavardhana (harsha)

COMMIT: http://review.gluster.org/7997 committed in master by Venky Shankar (vshankar) 
------
commit 665366a72b720d2eee61aba8b3108e12747db767
Author: Harshavardhana <harsha>
Date:   Thu Jun 5 13:17:24 2014 -0700

    geo-rep/gverify: Never use ping to check for host reachability
    
    On many linux distributions with iptables enabled, ICMP traffic
    is usually dropped even when port 22 is open for SSH service
    
    So practically `ping` is an unreliable command
    
    ~~~
    root@rhs1:/var/log/glusterfs # gluster volume geo-replication geo-test \
                              17.16.10.1::geo-test-slave create push-pem force
    172.16.10.1 not reachable.
    geo-replication command failed
    ~~~
    
    ~~~
    root@rhs1:/var/log/glusterfs # ping 172.16.10.1
    PING rhs2.sjc.redhat.com (172.16.10.1) 56(84) bytes of data.
    From rhs2.sjc.redhat.com (172.16.10.1) icmp_seq=1 Destination Host Prohibited
    ...
    ...
    ~~~
    
    ~~~
    root@rhs2:/var/log/glusterfs # service iptables status | grep 22
    4    ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:22
    root@rhs2:/var/log/glusterfs # service iptables status | grep icmp-host-prohibited
    25   REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited
    ~~~
    
    Change-Id: I33206ca071aa5d755c0762f7c486da222ec3c7db
    BUG: 1105337
    Signed-off-by: Harshavardhana <harsha>
    Reviewed-on: http://review.gluster.org/7997
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Aravinda VK <avishwan>
    Reviewed-by: Venky Shankar <vshankar>
    Tested-by: Venky Shankar <vshankar>

A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users