Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1515094

Summary: [RFE] tendrl should work with IP address
Product: Red Hat Gluster Storage Reporter: Saravanakumar <sarumuga>
Component: web-admin-tendrl-gluster-integrationAssignee: Nishanth Thomas <nthomas>
Status: CLOSED DUPLICATE QA Contact: sds-qe-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.3CC: mbukatov, mkarnik, mkudlej, nthomas, ppenicka, pprakash, rcyriac, rhs-bugs, rtalur, sankarshan, sarumuga
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 11:15:08 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:

Description Saravanakumar 2017-11-20 06:59:58 UTC
Description of problem:

It should be possible to configure tendrl with IP addresses. 
Currently, it supports FQDN based only.

CNS works based on IP addresses.
Also, it is possible to configure GlusterFS based on IP address.

So, tendrl should also works with IP address.

Version-Release number of selected component (if applicable):

How reproducible:
If you try to setup tendrl with IP addresses in configuration, it fails.  

Steps to Reproduce:

Actual results:

Expected results:
Configuration should succeed with IP address.

Additional info:

Comment 4 Martin Kudlej 2017-11-20 11:02:15 UTC
I'm changing product and component to proper one.

Comment 9 Nishanth Thomas 2018-10-16 11:15:08 UTC
This is fixed as part 1512937 and part of 3.4.0 release. hence closing this issue

*** This bug has been marked as a duplicate of bug 1512937 ***