Description of problem: man heketi-cli has typo in heketi-cli volume create --cluster section. -- part from man page -- heketi-cli volume create --cluster=<CLUSTER-ID> --disperse-data=<DISPERSION-VALUE> --durability=<TYPE> --name=<VOLUME-NAME> --redundancy=<REDUNDENCY-VALUE> --replica=<REPLICA- VALUE> --size=<VOLUME-SIZE> --snapshot-factor=<SNAPSHOT-FACTOR-VALUE> Create a GlusterFS volume Options --clusters="" --- ---- --- there is "cluster" and "clusters", valid / working is "clusters" Version-Release number of selected component (if applicable): rpm -qa | grep heketi heketi-5.0.0-2.el7rhgs.x86_64 python-heketi-5.0.0-2.el7rhgs.x86_64 heketi-client-5.0.0-2.el7rhgs.x86_64 How reproducible: always Steps to Reproduce: try to create volume using # heketi-cli volume create --cluster=cluster_id --size=1 Actual results: it will fail # heketi-cli volume create --cluster=78645dbaa6ce5f16c2162ef6ead4082a --size=1 Error: unknown flag: --cluster with "clusters" it will work. Expected results:
It's not an OpenShift bug, shifting to Gluster team. Please set the right version, I am really not sure.
Verified in man page: ################ Volume Commands heketi-cli volume create --clusters=<CLUSTER-IDS> --disperse-data=<DISPERSION-VALUE> --durability=<TYPE> --name=<VOLUME-NAME> --redundancy=<REDUNDENCY-VALUE> --replica=<REPLICA- VALUE> --size=<VOLUME-SIZE> --snapshot-factor=<SNAPSHOT-FACTOR-VALUE> Create a GlusterFS volume Options --clusters="" Optional: Comma separated list of cluster ids where this volume must be allocated. If omitted, Heketi will allocate the volume on any of the configured clusters which have the available space. Providing a set of clusters will ensure Heketi allocates storage for this volume only in the clusters specified. ################
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://access.redhat.com/errata/RHEA-2017:2879