Description of problem: #heketi-cli volume list output is currently missing the mapping between the Volume name and Volume ID. This makes a bit difficult for an admin to figure out which volume ID belongs to which volume. Version-Release number of selected component (if applicable): # heketi --version Heketi v1.3.0-dev-12-g2f52279 How reproducible: Always Steps to Reproduce: 1. Create a 4 node cluster and around 250+ volumes using heketi-cli 2. Execute # heketi-cli volume list to find out the Volume ID of any volume 3. Actual results: #'heketi-cli volume list' currently lists out ONLY the volume ID which makes an admin difficult to map the volume an ID relates to. In short, there is no easy way to figure a Volume ID of a particular volume. Even though we can somehow search and fetch this info using # heketi-cli topology info command, it's output will be huge considering the large no of volumes and bricks present in a scale out cluster. This makes it a bit difficult for anyone to find out a particular ID. ##### [root@dhcp42-197 ~]# heketi-cli volume list |head Volumes: 014e3d8c7902bca0a211c7adcc2a8419 0199691f38e037f3b7035631207712cc 0227b34bb83f5146792929a052e2232a 0230a6e9365dc3d84a064620a64af669 02f523532ff24b6fe0e92bc3b8a3becb 03143d7d19ef5c3e1306c156292ef812 066fa1ec604a59622dd43bc87bf1e6fb 06c428adbf4e507eb53b6013cdaac308 076c2bc0b6edd74d3e665239343a41db [root@dhcp42-197 ~]# heketi-cli volume list |wc -l 268 #### Expected results: heketi-cli volume list output should have Volumes -->> Volume ID mapping as well so it helps an admin to easily figure out a Volume ID of a particular volume Additional info:
I like this change! Thanks! https://github.com/heketi/heketi/issues/347
Fixed in 2.0.1
Verified as fixed: ###### # heketi-cli volume list Id:24bfa78486d666d5a783c8dbb16ba441 Cluster:9b142d683dd10583fc9292b07b135783 Name:vol001 Id:35fa9a028590db89c0b8fcd776d5d817 Cluster:9b142d683dd10583fc9292b07b135783 Name:vol007 Id:3c06e62884627c5c9f54fcaa598a9a2f Cluster:9b142d683dd10583fc9292b07b135783 Name:vol_3c06e62884627c5c9f54fcaa598a9a2f Id:53b7ec7ee88d883fc1d8d623832f3e87 Cluster:9b142d683dd10583fc9292b07b135783 Name:vol008 Id:72f1d0335103f42ea3155c48bd8d5411 Cluster:9b142d683dd10583fc9292b07b135783 Name:vol005 Id:7b97456a0f0aa6881394d09cf7026455 Cluster:9b142d683dd10583fc9292b07b135783 Name:vol010 Id:9ed36b7d4531b2fdf2f0a878f3c6a0e7 Cluster:9b142d683dd10583fc9292b07b135783 Name:heketidbstorage Id:aa9e325ffa66e98f939709d256c58a79 Cluster:9b142d683dd10583fc9292b07b135783 Name:vol003 Id:b344ab40ab0ea46ed484d0a718d9a0f7 Cluster:9b142d683dd10583fc9292b07b135783 Name:vol002 Id:ca50a7d041ddc2fdb524447f2f5774eb Cluster:9b142d683dd10583fc9292b07b135783 Name:vol009 Id:e7351253653a69f2b142957b7a8ee632 Cluster:9b142d683dd10583fc9292b07b135783 Name:vol006 Id:ff302039446fe1a13f198b10e95f6da3 Cluster:9b142d683dd10583fc9292b07b135783 Name:vol004 #######
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