Bug 1347041

Summary: Use node name instead of node label
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Luis Pabón <lpabon>
Component: heketiAssignee: Luis Pabón <lpabon>
Status: CLOSED ERRATA QA Contact: Prasanth <pprakash>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: hchiramm, madam, mliyazud, pprakash, rcyriac, ssaha
Target Milestone: ---Keywords: ZStream
Target Release: RHGS Container Converged 1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-04 04:51:09 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 Luis Pabón 2016-06-15 21:11:02 UTC 
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:
Comment 2 Luis Pabón 2016-06-15 21:11:49 UTC 
Upstream bug https://github.com/heketi/heketi/pull/383
Comment 8 errata-xmlrpc 2016-08-04 04:51:09 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