Bug 1294600 - [Tier]: Killing glusterfs tier process doesn't reflect as failed/faulty in tier status
Summary: [Tier]: Killing glusterfs tier process doesn't reflect as failed/faulty in ti...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tiering
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Mohammed Rafi KC
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On: 1294594
Blocks: 1295365
TreeView+ depends on / blocked
 
Reported: 2015-12-29 07:54 UTC by Mohammed Rafi KC
Modified: 2016-06-16 13:52 UTC (History)
5 users (show)

Fixed In Version: glusterfs-3.8rc2
Clone Of: 1294594
: 1295365 (view as bug list)
Environment:
Last Closed: 2016-06-16 13:52:41 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Vijay Bellur 2015-12-29 07:55:33 UTC
REVIEW: http://review.gluster.org/13107 (tier/glusterd: tier daemon not updating the status) posted (#1) for review on master by mohammed rafi  kc (rkavunga)

Comment 2 Vijay Bellur 2015-12-29 11:46:36 UTC
REVIEW: http://review.gluster.org/13107 (tier/glusterd: tier daemon not updating the status) posted (#2) for review on master by mohammed rafi  kc (rkavunga)

Comment 3 Vijay Bellur 2016-01-04 05:19:14 UTC
COMMIT: http://review.gluster.org/13107 committed in master by Atin Mukherjee (amukherj) 
------
commit fa4f583e469c065b4e1fb7ddfadfd14e1e6d62ae
Author: Mohammed Rafi KC <rkavunga>
Date:   Tue Dec 29 12:42:30 2015 +0530

    tier/glusterd: tier daemon not updating the status
    
    Tier process is not updating the status when the process killed
    mnually.
    
    Change-Id: Ia5ea903af78ff3582da2242e6058f11c71923fab
    BUG: 1294600
    Signed-off-by: Mohammed Rafi KC <rkavunga>
    Reviewed-on: http://review.gluster.org/13107
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>

Comment 4 Niels de Vos 2016-06-16 13:52:41 UTC
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.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


Note You need to log in before you can comment on or make changes to this bug.