[Bugs] [Bug 1472609] Root path xattr does not heal correctly in certain cases when volume is in stopped state

[bugzilla at redhat.com]

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



--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17824 committed in master by Raghavendra G
(rgowdapp at redhat.com) 
------
commit 777ad8f6a17d11e4582cf11d332a1a4d4c0c706f
Author: Sanoj Unnikrishnan <sunnikri at redhat.com>
Date:   Wed Jul 19 18:40:38 2017 +0530

    Heal root xattr correctly upon an add-brick operation

    When an add-brick is performed the root path xattr is healed using a hook
    script. For a volume in stopped state, the hook script is triggered in post
    op of add-brick. Otherwise, if the volume is in started state the hook
script
    is started on a subsequent volume start. The script unlinks itself after
    execution.
    The issue is that current hook script does not work when you have multiple
    volumes in stopped state. A hook script meant for volume1 can get trigerred
    during start of volume2.

    Fix: create separate hook script links for individual volumes.

    Bug: 1472609
    Change-Id: If5f056509505fdbbbf73d3363e9966047ae6a3d3
    Signed-off-by: Sanoj Unnikrishnan <sunnikri at redhat.com>
    Reviewed-on: https://review.gluster.org/17824
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp 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=JNn4LONRVn&a=cc_unsubscribe