Bug 1024434 - remove-brick status output fields are misaligned
remove-brick status output fields are misaligned
Product: GlusterFS
Classification: Community
Component: cli (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: bugs@gluster.org
Depends On:
  Show dependency treegraph
Reported: 2013-10-29 12:21 EDT by Joe Julian
Modified: 2015-10-07 09:15 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-10-07 09:15:58 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
replace-brick status output (427 bytes, text/plain)
2013-10-29 12:21 EDT, Joe Julian
no flags Details

  None (edit)
Description Joe Julian 2013-10-29 12:21:21 EDT
Created attachment 817134 [details]
replace-brick status output

Description of problem:
The fields in a remove-brick status do not align with their headers.

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

Steps to Reproduce:
1. create a volume
2. remove brick(s)
3. check the status

Actual results:
field values do not align with their headers

Expected results:
headers explain what the field values below them are

Additional info:
I think "skipped" is ... well... skipped.
Comment 1 Niels de Vos 2015-05-17 17:57:51 EDT
GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5.

This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "bugs@gluster.org".

If there is no response by the end of the month, this bug will get automatically closed.
Comment 2 Kaleb KEITHLEY 2015-10-07 09:15:58 EDT
GlusterFS 3.4.x has reached end-of-life.

If this bug still exists in a later release please reopen this and change the version or open a new bug.

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