Bug 1324300 - hostname is not populating in the error message when the operation fails
Summary: hostname is not populating in the error message when the operation fails
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Atin Mukherjee
QA Contact: Byreddy
URL:
Whiteboard:
Depends On:
Blocks: 1324717
TreeView+ depends on / blocked
 
Reported: 2016-04-06 04:35 UTC by Byreddy
Modified: 2018-01-02 08:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1324717 (view as bug list)
Environment:
Last Closed: 2018-01-02 08:11:03 UTC
Embargoed:


Attachments (Terms of Use)

Description Byreddy 2016-04-06 04:35:47 UTC
Description of problem:
=======================
hostname is not populating in the error message when remove-brick commit operation failed.



Version-Release number of selected component (if applicable):
=============================================================
glusterfs-3.7.9-1


How reproducible:
==================
Always


Steps to Reproduce:
===================
1. Create a two node cluster, create 2 *2 volume and start it
2. Fuse mount the volume and write enough data
3. start removing the one replica brick set  // this will trigger the rebalance
4. Try to commit remove-brick operation on both the nodes in sequence  and observe the error messages it's displaying on both the nodes.

Actual results:
===============
Hostname is missing in the error message

Expected results:
=================
Hostname should get populated in the error message when op fails.


Additional info:

Comment 3 Atin Mukherjee 2016-04-06 05:13:56 UTC
This doesn't impact any functionality apart from the non-uniformity of the error message reported back to the CLI. Hence setting both the severity and priority to low. We'll work on a upstream patch. Considering the severity can we move this bug to 3.2, Byreddy?

Comment 4 Byreddy 2016-04-07 04:19:23 UTC
(In reply to Atin Mukherjee from comment #3)
> This doesn't impact any functionality apart from the non-uniformity of the
> error message reported back to the CLI. Hence setting both the severity and
> priority to low. We'll work on a upstream patch. Considering the severity
> can we move this bug to 3.2, Byreddy?

This is not a regression and there is no any functionality loss here, only cli error message is incorrect so we can move this bug to 3.2

Comment 5 Atin Mukherjee 2016-04-07 05:41:05 UTC
Upstream patch http://review.gluster.org/13923 posted for review

Comment 9 Samikshan Bairagya 2017-08-09 10:51:57 UTC
We do not have a plan to fix this in 3.x. This should be fixed with glusterd2.

Comment 10 Atin Mukherjee 2018-01-02 08:11:03 UTC
Closing this bug as we don't plan to fix this in 3.x series. Also in GD2 the error handling will be more based on error codes.


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