Bug 1288517 - Data Tiering: new set of gluster v tier commands not working as expected
Summary: Data Tiering: new set of gluster v tier commands not working as expected
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tiering
Version: mainline
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
Assignee: hari gowtham
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On: 1283940
Blocks: 1291970
TreeView+ depends on / blocked
 
Reported: 2015-12-04 13:29 UTC by hari gowtham
Modified: 2016-06-16 13:48 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.8rc2
Doc Type: Bug Fix
Doc Text:
Clone Of: 1283940
: 1291970 (view as bug list)
Environment:
Last Closed: 2016-06-16 13:48:40 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Vijay Bellur 2015-12-04 13:32:32 UTC
REVIEW: http://review.gluster.org/12883 (tier : Error message of new tier commands on non tier volumes) posted (#1) for review on master by hari gowtham (hari.gowtham005)

Comment 2 Vijay Bellur 2015-12-07 10:14:34 UTC
REVIEW: http://review.gluster.org/12883 (tier/glusterd : making new tier detach command throw warning) posted (#2) for review on master by hari gowtham (hari.gowtham005)

Comment 3 Vijay Bellur 2015-12-09 11:59:59 UTC
REVIEW: http://review.gluster.org/12883 (tier/glusterd : making new tier detach command throw warning) posted (#3) for review on master by hari gowtham (hari.gowtham005)

Comment 4 Vijay Bellur 2015-12-10 05:37:25 UTC
REVIEW: http://review.gluster.org/12883 (tier/glusterd : making new tier detach command throw warning) posted (#4) for review on master by hari gowtham (hari.gowtham005)

Comment 5 Vijay Bellur 2015-12-10 06:56:13 UTC
REVIEW: http://review.gluster.org/12883 (tier/glusterd : making new tier detach command throw warning) posted (#5) for review on master by hari gowtham (hari.gowtham005)

Comment 6 Vijay Bellur 2015-12-14 10:30:10 UTC
REVIEW: http://review.gluster.org/12883 (tier/glusterd : making new tier detach command throw warning) posted (#6) for review on master by hari gowtham (hari.gowtham005)

Comment 7 Vijay Bellur 2015-12-15 06:12:33 UTC
REVIEW: http://review.gluster.org/12883 (tier/glusterd : making new tier detach command throw warning) posted (#7) for review on master by hari gowtham (hari.gowtham005)

Comment 8 Vijay Bellur 2015-12-15 09:20:50 UTC
REVIEW: http://review.gluster.org/12883 (tier/glusterd : making new tier detach command throw warning) posted (#8) for review on master by hari gowtham (hari.gowtham005)

Comment 9 Vijay Bellur 2015-12-16 03:45:51 UTC
COMMIT: http://review.gluster.org/12883 committed in master by Atin Mukherjee (amukherj) 
------
commit 55f4e8a74e89d61c97e79474c4488ba0bf40a3c1
Author: hari gowtham <hgowtham>
Date:   Fri Dec 4 18:34:36 2015 +0530

    tier/glusterd : making new tier detach command throw warning
    
    For detach tier, the validation was done using the string "detach-tier"
    but the new commands used has the string "tier". Making the string use
    "tier" to compare, creates problem as the tier status and tier detach
    have the keyword "tier". So tier detach and tier status were separated.
    and strtok was used to prevent the condition from passing when the
    volume name has a substring of "tier". (only the second word from the
    string is got and checked if the feature is tier)
    
    Problem: new detach tier command doesnt throw warnings like
    "not a tier volume" or " detach tier not started" respectively
    instead it prints empty output.
    
    Fix: while validate the volume is checked if its a tiered volume
    if yes it is checked if the detach tier is started, else a warning
    is thrown respectively.
    
    Change-Id: I94246d53b18ab0e9406beaf459eaddb7c5b766c2
    BUG: 1288517
    Signed-off-by: hari gowtham <hgowtham>
    Reviewed-on: http://review.gluster.org/12883
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Atin Mukherjee <amukherj>

Comment 10 Niels de Vos 2016-06-16 13:48:40 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.