Bug 1215517

Summary: [New] - Distribute replicate volume type is shown as Distribute Stripe in the output of gluster volume info <volname> --xml
Product: [Community] GlusterFS Reporter: Atin Mukherjee <amukherj>
Component: cliAssignee: Atin Mukherjee <amukherj>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.7.0CC: amukherj, bugs, gluster-bugs, knarra
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.7.0beta1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1212398 Environment:
Last Closed: 2015-05-14 17:27:26 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: 1212398    
Bug Blocks: 1186580, 1212418    

Description Atin Mukherjee 2015-04-27 04:57:29 UTC
+++ This bug was initially created as a clone of Bug #1212398 +++

Description of problem:
When user creates a distribute replicate volume in the "gluster vol info <vol_name> --xml it is shown as distribute stripe.

Pasting the output here:

gluster vol info vol_dis_rep --xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<cliOutput>
  <opRet>0</opRet>
  <opErrno>0</opErrno>
  <opErrstr/>
  <volInfo>
    <volumes>
      <volume>
        <name>vol_dis_rep</name>
        <id>15b7e3bf-116f-4d24-8589-274cfde92ea5</id>
        <status>0</status>
        <statusStr>Created</statusStr>
        <brickCount>4</brickCount>
        <distCount>2</distCount>
        <stripeCount>1</stripeCount>
        <replicaCount>2</replicaCount>
        <disperseCount>0</disperseCount>
        <redundancyCount>0</redundancyCount>
        <type>6</type>
        <typeStr>Distributed-Stripe</typeStr>
        <transport>0</transport>
        <xlators/>
        <bricks>
          <brick uuid="83c52dea-d22d-44e3-adf2-9cfecbcd45c2">10.70.37.199:/rhs/brick3/b1<name>10.70.37.199:/rhs/brick3/b1</name><hostUuid>83c52dea-d22d-44e3-adf2-9cfecbcd45c2</hostUuid></brick>
          <brick uuid="df227fe6-fe66-42ef-b7c7-0031a4f5deeb">10.70.37.208:/rhs/brick3/b2<name>10.70.37.208:/rhs/brick3/b2</name><hostUuid>df227fe6-fe66-42ef-b7c7-0031a4f5deeb</hostUuid></brick>
          <brick uuid="83c52dea-d22d-44e3-adf2-9cfecbcd45c2">10.70.37.199:/rhs/brick4/b3<name>10.70.37.199:/rhs/brick4/b3</name><hostUuid>83c52dea-d22d-44e3-adf2-9cfecbcd45c2</hostUuid></brick>
          <brick uuid="df227fe6-fe66-42ef-b7c7-0031a4f5deeb">10.70.37.208:/rhs/brick4/b4<name>10.70.37.208:/rhs/brick4/b4</name><hostUuid>df227fe6-fe66-42ef-b7c7-0031a4f5deeb</hostUuid></brick>
        </bricks>
        <optCount>3</optCount>
        <options>
          <option>
            <name>auth.allow</name>
            <value>*</value>
          </option>
          <option>
            <name>user.cifs</name>
            <value>enable</value>
          </option>
          <option>
            <name>nfs.disable</name>
            <value>off</value>
          </option>
        </options>
      </volume>
      <count>1</count>
    </volumes>
  </volInfo>
</cliOutput>


Version-Release number of selected component (if applicable):
glusterfs-3.7dev-0.994.gitf522001.el6.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Create a volume of distribute replicate.
2. check the xml ouput of gluster vol info.
3.

Actual results:
gluster vol info xml output shows the volume type as "distribute stripe"

Expected results:
volume type should be displayed correctly.

Additional info:

--- Additional comment from Anand Avati on 2015-04-16 08:18:26 EDT ---

REVIEW: http://review.gluster.org/10271 (cli: fix vol_type in volume info xml) posted (#1) for review on master by Atin Mukherjee (amukherj)

--- Additional comment from Anand Avati on 2015-04-21 00:28:55 EDT ---

REVIEW: http://review.gluster.org/10271 (cli: fix vol_type in volume info xml) posted (#3) for review on master by Atin Mukherjee (amukherj)

--- Additional comment from Anand Avati on 2015-04-23 00:36:58 EDT ---

REVIEW: http://review.gluster.org/10271 (cli: fix vol_type in volume info xml) posted (#4) for review on master by Atin Mukherjee (amukherj)

--- Additional comment from Anand Avati on 2015-04-27 00:54:32 EDT ---

COMMIT: http://review.gluster.org/10271 committed in master by Kaushal M (kaushal) 
------
commit 4c3724f195240e40994b71add255f85ee1b025fb
Author: Atin Mukherjee <amukherj>
Date:   Thu Apr 16 17:45:04 2015 +0530

    cli: fix vol_type in volume info xml
    
    xml parsing of voltype should be inline with the cli
    
    Change-Id: I41ddddac00d07f03b56a041e1c3f5a132fbd7393
    BUG: 1212398
    Signed-off-by: Atin Mukherjee <amukherj>
    Reviewed-on: http://review.gluster.org/10271
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Kaushal M <kaushal>

Comment 1 Anand Avati 2015-04-27 04:58:18 UTC
REVIEW: http://review.gluster.org/10396 (cli: fix vol_type in volume info xml) posted (#1) for review on release-3.7 by Atin Mukherjee (amukherj)

Comment 2 Anand Avati 2015-04-27 08:27:27 UTC
REVIEW: http://review.gluster.org/10396 (cli: fix vol_type in volume info xml) posted (#2) for review on release-3.7 by Atin Mukherjee (amukherj)

Comment 3 Anand Avati 2015-04-28 08:55:27 UTC
COMMIT: http://review.gluster.org/10396 committed in release-3.7 by Krishnan Parthasarathi (kparthas) 
------
commit 00a74ad99ec3ee2090aff0849ab95458941aaaec
Author: Atin Mukherjee <amukherj>
Date:   Thu Apr 16 17:45:04 2015 +0530

    cli: fix vol_type in volume info xml
    
    xml parsing of voltype should be inline with the cli
    
    Backport of http://review.gluster.org/10271
    
    Change-Id: I41ddddac00d07f03b56a041e1c3f5a132fbd7393
    BUG: 1215517
    Signed-off-by: Atin Mukherjee <amukherj>
    Reviewed-on: http://review.gluster.org/10271
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Kaushal M <kaushal>
    (cherry picked from commit 4c3724f195240e40994b71add255f85ee1b025fb)
    Reviewed-on: http://review.gluster.org/10396
    Reviewed-by: Krishnan Parthasarathi <kparthas>

Comment 4 Niels de Vos 2015-05-14 17:27:26 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 5 Niels de Vos 2015-05-14 17:28:48 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 6 Niels de Vos 2015-05-14 17:35:20 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user