[Bugs] [Bug 1397705] New: PEER_REJECT, EVENT_BRICKPATH_RESOLVE_FAILED, EVENT_COMPARE_FRIEND_VOLUME_FAILED are not seen

[bugzilla at redhat.com]

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

            Bug ID: 1397705
           Summary: PEER_REJECT, EVENT_BRICKPATH_RESOLVE_FAILED,
                    EVENT_COMPARE_FRIEND_VOLUME_FAILED are not seen
           Product: GlusterFS
           Version: 3.9
         Component: glusterd
          Keywords: Triaged
          Assignee: bugs at gluster.org
          Reporter: amukherj at redhat.com
                CC: bugs at gluster.org
        Depends On: 1397424
            Blocks: 1397430



+++ This bug was initially created as a clone of Bug #1397424 +++

Description of problem:

1. PEER_REJECT event is not seen if the peer add request is from an unknown
peer
during peer handshaking.
2. EVENT_COMPARE_FRIEND_VOLUME_FAILED is not seen if there is a checksum
mismatch in friend volume
3. EVENT_BRICKPATH_RESOLVE_FAILED event is not seen if glusterd fails to
restore bricks and fails to come up.
4. Remove EVENT_BRICKS_START_FAILED event as we already have
EVENT_BRICK_START_FAILED

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Worker Ant on 2016-11-22 08:53:34 EST ---

REVIEW: http://review.gluster.org/15903 (glusterd: fix few events generation)
posted (#1) for review on master by Atin Mukherjee (amukherj at redhat.com)

--- Additional comment from Worker Ant on 2016-11-23 03:45:02 EST ---

COMMIT: http://review.gluster.org/15903 committed in master by Atin Mukherjee
(amukherj at redhat.com) 
------
commit 63a4f5da0feb19e47d16aa2d6aa78efaef1c93ca
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Tue Nov 22 19:04:54 2016 +0530

    glusterd: fix few events generation

    This patch does the following:
    1. Generate PEER_REJECT event if the peer add request is from an unknown
peer
    during peer handshaking.
    2. EVENT_COMPARE_FRIEND_VOLUME_FAILED should be generated based on status
code,
    not ret.
    3. Add EVENT_BRICKPATH_RESOLVE_FAILED event in case glusterd fails to
resolve
    bricks, this is mainly at restore path.
    4. Remove EVENT_BRICKS_START_FAILED event as we already have
    EVENT_BRICK_START_FAILED

    Change-Id: I90e5bc4a331166d0bb3554eb2ec9df2526837a1d
    BUG: 1397424
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: http://review.gluster.org/15903
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan at gmail.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1397424
[Bug 1397424] PEER_REJECT, EVENT_BRICKPATH_RESOLVE_FAILED,
EVENT_COMPARE_FRIEND_VOLUME_FAILED are not seen
https://bugzilla.redhat.com/show_bug.cgi?id=1397430
[Bug 1397430] PEER_REJECT, EVENT_BRICKPATH_RESOLVE_FAILED,
EVENT_COMPARE_FRIEND_VOLUME_FAILED are not seen
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.