Bug 1279350 - [Tier]: Space is missed b/w the words in the detach tier stop error message
Summary: [Tier]: Space is missed b/w the words in the detach tier stop error message
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: tier
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
high
low
Target Milestone: ---
: RHGS 3.1.2
Assignee: hari gowtham
QA Contact: Nag Pavan Chilakam
URL:
Whiteboard:
Depends On:
Blocks: 1260783 1260923 1283488 1283856
TreeView+ depends on / blocked
 
Reported: 2015-11-09 09:15 UTC by Byreddy
Modified: 2016-09-17 15:40 UTC (History)
5 users (show)

Fixed In Version: glusterfs-3.7.5-7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1283488 (view as bug list)
Environment:
Last Closed: 2016-03-01 05:54:04 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0193 0 normal SHIPPED_LIVE Red Hat Gluster Storage 3.1 update 2 2016-03-01 10:20:36 UTC

Description Byreddy 2015-11-09 09:15:18 UTC
Description of problem:
=======================
The error message getting when detach tier stop is failed is incorrect, error message words are concatenated. ( Detach-tiernot )

# gluster volume detach-tier Dis stop
volume detach-tier stop: failed: Detach-tiernot started  // Expected space b/w  Detach-tier and not



Version-Release number of selected component (if applicable):
=============================================================
glusterfs-3.7.5-5


How reproducible:
=================
100%

Steps to Reproduce:
===================
1. Have two node cluster
2. Create replica volume type (1*2) and start it
3. Attach a tier of type distributed (1*1)
4. Stop the detach tier //it will fail, check the failure message

Actual results:
===============
Space is missing b/w the words in the error message
 
Expected results:
=================
Space is required b/w the words in the error message

Additional info:

Comment 3 Nag Pavan Chilakam 2015-11-24 16:49:32 UTC
With 3.7.5-7
Volume Name: remove
Type: Tier
Volume ID: 1f06ca40-384f-4b74-a614-f05903cdbdca
Status: Started
Number of Bricks: 8
Transport-type: tcp
Hot Tier :
Hot Tier Type : Distributed-Replicate
Number of Bricks: 2 x 2 = 4
Brick1: yarrow:/rhs/brick6/remove_hh
Brick2: zod:/rhs/brick6/remove_hh
Brick3: yarrow:/rhs/brick7/remove_hh
Brick4: zod:/rhs/brick7/remove_hh
Cold Tier:
Cold Tier Type : Distributed-Replicate
Number of Bricks: 2 x 2 = 4
Brick5: zod:/rhs/brick2/remove
Brick6: yarrow:/rhs/brick2/remove
Brick7: zod:/rhs/brick3/remove
Brick8: yarrow:/rhs/brick3/remove
Options Reconfigured:
cluster.tier-mode: cache
features.ctr-enabled: on
performance.readdir-ahead: on
[root@zod ~]# gluster v detach-tier remove stop
volume detach-tier stop: failed: Detach-tier not started
Tier command failed
[root@zod ~]# 




But, it doens't work with the newer cli structure as below:
[root@zod ~]# gluster v tier remove detach stop
                                    Node Rebalanced-files          size       scanned      failures       skipped               status   run time in secs
                               ---------      -----------   -----------   -----------   -----------   -----------         ------------     --------------
                               localhost                0        0Bytes         12000             0             0              stopped           14725.00
                             10.70.34.43                0        0Bytes         12261             0             0              stopped           14726.00
'detach-tier' process may be in the middle of a file migration.
The process will be fully stopped once the migration of the file is complete.
Please check detach-tier process for completion before doing any further brick related tasks on the volume.
[root@zod ~]# 



For this we are anyway having a bug 1283940
which should be fixed

Comment 5 errata-xmlrpc 2016-03-01 05:54:04 UTC
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


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