Bug 1683526 - rebalance start command doesn't throw up error message if the command fails
Summary: rebalance start command doesn't throw up error message if the command fails
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 4.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sanju
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1699176 1713613
TreeView+ depends on / blocked
 
Reported: 2019-02-27 06:34 UTC by Atin Mukherjee
Modified: 2019-05-24 09:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1699176 (view as bug list)
Environment:
Last Closed: 2019-04-12 02:18:46 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Atin Mukherjee 2019-02-27 06:34:35 UTC
Description of problem:

When a rebalance start command fails, it doesn't throw up the error message back to CLI.

Version-Release number of selected component (if applicable):
release-6

How reproducible:
Always

Steps to Reproduce:
1. Create 1 X 1 volume, trigger rebalance start. Command fails as glusterd.log complains about following

[2019-02-27 06:29:15.448303] E [MSGID: 106218] [glusterd-rebalance.c:462:glusterd_rebalance_cmd_validate] 0-glusterd: Volume test-vol5 is not a distribute type or contains only 1 brick

But CLI doesn't throw up any error messages.

Actual results:
CLI doesn't throw up an error message.

Expected results:
CLI should throw up an error message.


Additional info:

Comment 1 Worker Ant 2019-04-11 12:50:42 UTC
REVIEW: https://review.gluster.org/22547 (glusterd: display an error when rebalance start is failed) posted (#1) for review on master by Sanju Rakonde

Comment 2 Worker Ant 2019-04-12 02:14:57 UTC
REVISION POSTED: https://review.gluster.org/22547 (glusterd: display an error when rebalance start is failed) posted (#2) for review on master by Sanju Rakonde

Comment 3 Sanju 2019-04-12 02:18:46 UTC
A patch has posted for review at upstream master to fix this issue. As we cannot fix this BZ in 4.1 closing this BZ as won't fix.

link to the patch: https://review.gluster.org/#/c/glusterfs/+/22547/

Thanks,
Sanju


Note You need to log in before you can comment on or make changes to this bug.