Bug 1227241

Summary: cli/tiering:typo errors in tiering
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Mohammed Rafi KC <rkavunga>
Component: tierAssignee: Mohammed Rafi KC <rkavunga>
Status: CLOSED ERRATA QA Contact: Nag Pavan Chilakam <nchilaka>
Severity: high Docs Contact:
Priority: high    
Version: rhgs-3.1CC: bugs, rhs-bugs, storage-qa-internal, trao
Target Milestone: ---Keywords: Triaged
Target Release: RHGS 3.1.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1226024 Environment:
Last Closed: 2015-07-29 04:54:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1226024    
Bug Blocks: 1202842    

Description Mohammed Rafi KC 2015-06-02 08:47:54 UTC 
+++ This bug was initially created as a clone of Bug #1226024 +++

Description of problem:

    
    volume info shows Cold Bricks instead of Tier type
      eg:
    Volume Name: patchy2
    Type: Tier
    Volume ID: 28c25b8d-b8a1-45dc-b4b7-cbd0b344f58f
    Status: Started
    Number of Bricks: 3
    Transport-type: tcp
    Hot Tier :
    Hot Tier Type : Distribute
    Number of Bricks: 1
    Brick1: 10.70.1.35:/home/brick43
    Cold Bricks:
    Cold Tier Type : Distribute
    Number of Bricks: 2
    Brick2: 10.70.1.35:/home/brick19
    Brick3: 10.70.1.35:/home/brick16
    Options Reconfigured:
    


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 Anand Avati on 2015-05-28 15:03:18 EDT ---

REVIEW: http://review.gluster.org/10978 (tiering: Correct errors in cli and glusterd) posted (#1) for review on release-3.7 by mohammed rafi  kc (rkavunga)

--- Additional comment from Anand Avati on 2015-06-01 00:31:56 EDT ---

COMMIT: http://review.gluster.org/10978 committed in release-3.7 by Kaushal M (kaushal) 
------
commit 57abe450c1e90749a4a32247836f05b1195d5313
Author: Mohammed Rafi KC <rkavunga>
Date:   Wed May 13 16:53:22 2015 +0530

    tiering: Correct errors in cli and glusterd
    
            Back port of http://review.gluster.org/10768
    
    Problem 1:
    
    volume info shows Cold Bricks instead of Tier type
      eg:
    Volume Name: patchy2
    Type: Tier
    Volume ID: 28c25b8d-b8a1-45dc-b4b7-cbd0b344f58f
    Status: Started
    Number of Bricks: 3
    Transport-type: tcp
    Hot Tier :
    Hot Tier Type : Distribute
    Number of Bricks: 1
    Brick1: 10.70.1.35:/home/brick43
    Cold Bricks:
    Cold Tier Type : Distribute
    Number of Bricks: 2
    Brick2: 10.70.1.35:/home/brick19
    Brick3: 10.70.1.35:/home/brick16
    Options Reconfigured:
    
    Problem 2: Detach-tier sending enums of Rebalance
    
       detach-tier has it's own Enum to send with detach-tier command,
    using that enums will make more appropriate.
    
    Problem 3:
    
    Wrongly sets hot_brick count during the dictionary copying for response
    
    >Change-Id: Icc054a999a679456881bc70511470d32ff8a86e4
    >BUG: 1211264
    >Signed-off-by: Mohammed Rafi KC <rkavunga>
    >Reviewed-on: http://review.gluster.org/10768
    >Reviewed-by: Atin Mukherjee <amukherj>
    >Reviewed-by: Kaushal M <kaushal>
    >Tested-by: Gluster Build System <jenkins.com>
    >Tested-by: NetBSD Build System
    
    Change-Id: I889d3b83a1f197b79eb71e594a1ad1f2037ed402
    BUG: 1226024
    Signed-off-by: Mohammed Rafi KC <rkavunga>
    Reviewed-on: http://review.gluster.org/10978
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Joseph Fernandes
    Reviewed-by: Kaushal M <kaushal>

--- Additional comment from Niels de Vos on 2015-06-02 04:03:51 EDT ---

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.7.1, please reopen this bug report.

glusterfs-3.7.1 has been announced on the Gluster Packaging mailinglist [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://thread.gmane.org/gmane.comp.file-systems.gluster.packaging/1
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
Comment 3 Triveni Rao 2015-06-11 18:25:50 UTC 
this bug is verified and found no issues

[root@rhsqa14-vm1 ~]# gluster v info
 
Volume Name: venus
Type: Tier
Volume ID: ad3a7752-93f3-4a61-8b3c-b40bc5d9af4a
Status: Started
Number of Bricks: 6
Transport-type: tcp
Hot Tier :
Hot Tier Type : Replicate
Number of Bricks: 1 x 2 = 2
Brick1: 10.70.47.163:/rhs/brick3/m0
Brick2: 10.70.47.165:/rhs/brick3/m0
Cold Tier:
Cold Tier Type : Distributed-Replicate
Number of Bricks: 2 x 2 = 4
Brick3: 10.70.47.165:/rhs/brick1/m0
Brick4: 10.70.47.163:/rhs/brick1/m0
Brick5: 10.70.47.165:/rhs/brick2/m0
Brick6: 10.70.47.163:/rhs/brick2/m0
Options Reconfigured:
performance.readdir-ahead: on
[root@rhsqa14-vm1 ~]#
Comment 4 Triveni Rao 2015-06-12 11:12:48 UTC 
[root@rhsqa14-vm1 ~]# glusterfs --version
glusterfs 3.7.1 built on Jun  9 2015 02:31:54
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2013 Red Hat, Inc. <http://www.redhat.com/>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
It is licensed to you under your choice of the GNU Lesser
General Public License, version 3 or any later version (LGPLv3
or later), or the GNU General Public License, version 2 (GPLv2),
in all cases as published by the Free Software Foundation.
[root@rhsqa14-vm1 ~]# rpm -qa | grep gluster
glusterfs-3.7.1-1.el6rhs.x86_64
glusterfs-cli-3.7.1-1.el6rhs.x86_64
glusterfs-libs-3.7.1-1.el6rhs.x86_64
glusterfs-client-xlators-3.7.1-1.el6rhs.x86_64
glusterfs-fuse-3.7.1-1.el6rhs.x86_64
glusterfs-server-3.7.1-1.el6rhs.x86_64
glusterfs-api-3.7.1-1.el6rhs.x86_64
[root@rhsqa14-vm1 ~]#
Comment 6 errata-xmlrpc 2015-07-29 04:54:59 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-1495.html