[Bugs] [Bug 1462200] glusterd status showing failed when it's stopped in RHEL7

bugzilla at redhat.com bugzilla at redhat.com
Mon Jun 19 12:41:36 UTC 2017


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



--- Comment #7 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17559 committed in master by Atin Mukherjee
(amukherj at redhat.com) 
------
commit 52d0886cfbcdfd69fa0cac0a6d51cd8811d8c6d7
Author: Gaurav Yadav <gyadav at redhat.com>
Date:   Sun Jun 18 23:10:57 2017 +0530

    glusterd.service (systemd), shows "Active failed" when gd in stop state

    While doing cleanupandexit glusterd was handling the signal SIGTERM which
    is clean exit but systemd treats it as failure being a non-zero value.

    With this fix dependency "SuccessExitStatus " has been added
    in glusterd.service which takes care of service stop properly.

    Signed-off-by: Gaurav Yadav <gyadav at redhat.com>

    Change-Id: Ie5216722632a245f787fd69bfbbf8d0f0068bccb
    BUG: 1462200
    Reviewed-on: https://review.gluster.org/17559
    Tested-by: Gaurav Yadav <gyadav at redhat.com>
    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: Prashanth Pai <ppai 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=3o8AimfIja&a=cc_unsubscribe


More information about the Bugs mailing list