Description of problem: Failed to show rebalance status if the volume name has 'tier' substring Version-Release number of selected component (if applicable): glusterfs-server-3.7.5-8.el7rhgs.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a volume with volume name tiervol 2. Start the rebalance on volume 3. Do gluster volume rebalance status. Actual results: Rebalance status should be displayed. Expected results: Errorring out with the message, "volume rebalance: tiervol: failed: volume tiervol is not a tier volume." Additional info: [root@node71 ~]# gluster vol info Volume Name: tiervol Type: Distributed-Replicate Volume ID: 4a458535-e1d4-4e54-b4fd-47661cb9d0b5 Status: Created Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: 10.70.46.236:/bricks/brick0/tiervol_brick0 Brick2: 10.70.46.203:/bricks/brick0/tiervol_brick1 Brick3: 10.70.46.236:/bricks/brick1/tiervol_brick2 Brick4: 10.70.46.203:/bricks/brick1/tiervol_brick3 Options Reconfigured: performance.readdir-ahead: on [root@node71 ~]# [root@node71 ~]# gluster volume rebalance tiervol fix-layout start volume rebalance: tiervol: success: Rebalance on tiervol has been started successfully. Use rebalance status command to check status of the rebalance process. ID: 6e12d9ff-57f5-4a5f-bd06-2afd2cf984e1 [root@node71 ~]# gluster volume rebalance tiervol status volume rebalance: tiervol: failed: volume tiervol is not a tier volume. [root@node71 ~]#
This patch will be fixed by the patch mentioned below. http://review.gluster.org/#/c/12883/ (upstream)
The Downstream patch for that is: https://code.engineering.redhat.com/gerrit/#/c/63889/ (Merged)
Tested and verified this on the build glusterfs-3.7.5-12.el7rhgs.x86_64 Tried out different combinations of volume name (with tier substring in it) and performed a rebalance, which worked as expected. Moving this bug to verified in 3.0.2. Detailed logs are attached!
Created attachment 1108557 [details] server logs
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/RHBA-2016-0193.html