Bug 1276340 - [heketi-cli] Inconsistency with the requirement for zone value
[heketi-cli] Inconsistency with the requirement for zone value
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: heketi (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: RHGS 3.1.2
Assigned To: Luis Pabón
Anush Shetty
: ZStream
Depends On:
Blocks: 1260783
  Show dependency treegraph
Reported: 2015-10-29 09:41 EDT by Anush Shetty
Modified: 2016-11-08 17:24 EST (History)
3 users (show)

See Also:
Fixed In Version: heketi-1.0.1-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-03-01 00:48:57 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Anush Shetty 2015-10-29 09:41:43 EDT
Description of problem: When the nodes are added through a topology file, zone value isn't mandatory but adding a node through cli expects a zone value. 

Version-Release number of selected component (if applicable): heketi-devel-1.0.0-1.el7rhgs.noarch

How reproducible: Always

Additional info:


# heketi-cli -user="admin" -secret="Top Secret" node add -cluster=fe5f47e19eaafb538baa429c734a647c -management-host-name=hostname

Error: Missing zone

But this worked:

#heketi-cli load -json=topology.json

cat topology.json
    "clusters": [
            "nodes": [
                    "node": {
                        "hostnames": {
                            "manage": [
                            "storage": [

                    "devices": [
Comment 2 Luis Pabón 2015-10-29 21:32:42 EDT
Github issue: https://github.com/heketi/heketi/issues/236
Comment 4 Anush Shetty 2015-11-09 01:50:52 EST
Verified with heketi-1.0.1-1.el7rhgs.x86_64
Comment 6 errata-xmlrpc 2016-03-01 00:48:57 EST
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.


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