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:
REVIEW: http://review.gluster.org/10271 (cli: fix vol_type in volume info xml) posted (#1) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/10271 (cli: fix vol_type in volume info xml) posted (#3) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/10271 (cli: fix vol_type in volume info xml) posted (#4) for review on master by Atin Mukherjee (amukherj)
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>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
Fix for this bug is already made in a GlusterFS release. The cloned BZ has details of the fix and the release. Hence closing this mainline BZ.
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