[Bugs] [Bug 1317861] Probing a new node, which is part of another cluster, should throw proper error message in logs and CLI

bugzilla at redhat.com bugzilla at redhat.com
Tue Mar 22 07:06:18 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1317861



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13741 committed in release-3.7 by Atin
Mukherjee (amukherj at redhat.com) 
------
commit 2512bb829a10d9d087a0c7d2a4217b90b60e3845
Author: Gaurav Kumar Garg <garg.gaurav52 at gmail.com>
Date:   Tue Aug 11 18:17:31 2015 +0530

    glusterd: probing a new node, which is part of another cluster should give
error

    This patch is backport of: http://review.gluster.org/#/c/11884/

    If user try to add node to extant cluster using "gluster peer probe \
    <ip/hostname>" command then command is failing but its not giving
    proper cause of failure.

    This fix will take control of proper error message during peer probe
    with already extant cluster.

    Change-Id: I4f993e78c0e1b3e061153b984ec5e9b70085aef5
    BUG: 1317861
    Signed-off-by: Gaurav Kumar Garg <ggarg at redhat.com>

      >> Change-Id: I4f993e78c0e1b3e061153b984ec5e9b70085aef5
      >> BUG: 1252448
      >> Signed-off-by: Gaurav Kumar Garg <ggarg at redhat.com>
      >> Reviewed-on: http://review.gluster.org/11884
      >> Tested-by: NetBSD Build System <jenkins at build.gluster.org>
      >> Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    (cherry picked from commit 31a36dca20a976b143cc5c970e115d8d36df847a)

    Change-Id: I0066d8b3b70346b123ab5f3b32a6cf8e54d242fc
    Reviewed-on: http://review.gluster.org/13741
    Tested-by: Gaurav Kumar Garg <ggarg at redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=WOpzf7eTNv&a=cc_unsubscribe


More information about the Bugs mailing list