Description of problem: Instead of having the administrator create a label for Heketi to find the pod, use the name of the node during the glusterfs deployment. Usage would be as follows: [vagrant@client ~]$ oc get nodes NAME STATUS AGE 192.168.121.168 Ready 9d 192.168.121.172 Ready 9d 192.168.121.233 Ready 9d $ oc process glusterfs -v GLUSTERFS_NODE=192.168.121.168 | oc create -f - $ oc process glusterfs -v GLUSTERFS_NODE=192.168.121.172 | oc create -f - $ oc process glusterfs -v GLUSTERFS_NODE=192.168.121.233 | oc create -f - Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Upstream bug https://github.com/heketi/heketi/pull/383
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