Bug 1337852

Summary: RFE: Rename "Id:" in # heketi-cli volume info <Id> output to "Volume Id:"
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Prasanth <pprakash>
Component: heketiAssignee: Luis Pabón <lpabon>
Status: CLOSED ERRATA QA Contact: Prasanth <pprakash>
Severity: low Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: madam, mliyazud, pprakash, rcyriac
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: RHGS Container Converged 1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-04 04:50:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1332128    

Description Prasanth 2016-05-20 09:07:08 UTC 
Description of problem:

"Id:" in # heketi-cli volume info <Id> output should be changed to "Volume Id:" to make it consistent across all the "info" outputs

Version-Release number of selected component (if applicable):
# heketi --version
Heketi v1.3.0-dev-12-g2f52279

How reproducible: Always


Steps to Reproduce:
1. # heketi-cli volume info <Id>


Actual results: See the output below. It currently shows as "Id: ff195d92c6a1f5f9f55d5877e90b07cf". To make it consistent across all the "info" outputs and as a standard practice, it should be renamed as "Volume Id: <Id>"

######
# heketi-cli volume info ff195d92c6a1f5f9f55d5877e90b07cf
Name: vol154
Size: 10
Id: ff195d92c6a1f5f9f55d5877e90b07cf
Cluster Id: ac8d5f061b670e18d5c9a2f6dbfb1228
Mount: 10.70.42.85:vol154
Mount Options: backupvolfile-servers=10.70.42.222,10.70.43.158
Durability Type: replicate
Replica: 3
Snapshot: Disabled

Bricks:
Id: 2837b398ccb6b703c5edc369f03105df
Path: /var/lib/heketi/mounts/vg_105575102a1b6b1db8464506c14f4fdd/brick_2837b398ccb6b703c5edc369f03105df/brick
Size (GiB): 5
Node: e328247d957216630e77c7ed90ae1a89
Device: 105575102a1b6b1db8464506c14f4fdd

Id: 3af3b55e5610a54032eb602fdf2ba472
Path: /var/lib/heketi/mounts/vg_b692d3c9c953ec2f832f9ca947802ca7/brick_3af3b55e5610a54032eb602fdf2ba472/brick
Size (GiB): 5
Node: 15eb9c55772ce9eb6b31b08180bdcb1b
Device: b692d3c9c953ec2f832f9ca947802ca7

Id: 58d5cbac37134c3b0ca50e2cd5cf31ed
Path: /var/lib/heketi/mounts/vg_5013101181241c140bd579f226cfd3d1/brick_58d5cbac37134c3b0ca50e2cd5cf31ed/brick
Size (GiB): 5
Node: e328247d957216630e77c7ed90ae1a89
Device: 5013101181241c140bd579f226cfd3d1

Id: 76c9d5f210bc0cfb34ce625c7a825057
Path: /var/lib/heketi/mounts/vg_941c81a251cd613a673506f4e342c9df/brick_76c9d5f210bc0cfb34ce625c7a825057/brick
Size (GiB): 5
Node: 15eb9c55772ce9eb6b31b08180bdcb1b
Device: 941c81a251cd613a673506f4e342c9df

Id: bf623cf413f2cd484acd67aaf11d524e
Path: /var/lib/heketi/mounts/vg_17808d0c2e35f3a16a998c5c5820a904/brick_bf623cf413f2cd484acd67aaf11d524e/brick
Size (GiB): 5
Node: f38f74314ef11e2b575dd280bb5f31f5
Device: 17808d0c2e35f3a16a998c5c5820a904

Id: bffca053ad47942a3acdeac940c6864d
Path: /var/lib/heketi/mounts/vg_65f837f8e26d1afb8b2050194afd0203/brick_bffca053ad47942a3acdeac940c6864d/brick
Size (GiB): 5
Node: f38f74314ef11e2b575dd280bb5f31f5
Device: 65f837f8e26d1afb8b2050194afd0203
#######
Comment 1 Luis Pabón 2016-05-24 18:36:44 UTC 
https://github.com/heketi/heketi/issues/346
Comment 3 Luis Pabón 2016-06-02 06:14:35 UTC 
fixed by Heketi 2.0.0
Comment 7 Prasanth 2016-06-06 06:04:56 UTC 
Verified as fixed in heketi-client-2.0.0-1.el7rhgs.x86_64

###########
# heketi-cli volume info 65e5fc4846290df01743c4244c0a2fcc
Name: vol_65e5fc4846290df01743c4244c0a2fcc
Size: 100
Volume Id: 65e5fc4846290df01743c4244c0a2fcc
Cluster Id: ba6aca5e5d02c69800d230e53a7aae78
Mount: 10.70.43.202:vol_65e5fc4846290df01743c4244c0a2fcc
Mount Options: backup-volfile-servers=10.70.42.221,10.70.43.156
Durability Type: replicate
Replica: 3
Snapshot: Disabled
###########
Comment 9 errata-xmlrpc 2016-08-04 04:50:38 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-1498.html