Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1420929 - WebUI should warn if a hostname is entered for Gluster Endpoint during OCP deployment, hostnames are not supported by OCP for gluster.
Summary: WebUI should warn if a hostname is entered for Gluster Endpoint during OCP de...
Status: NEW
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: WebUI
Version: 1.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 1.2
Assignee: John Matthews
QA Contact: Sudhir Mallamprabhakara
Depends On:
Blocks: 1421239
TreeView+ depends on / blocked
Reported: 2017-02-09 22:01 UTC by James Olin Oden
Modified: 2020-01-08 16:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1421239 (view as bug list)
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description James Olin Oden 2017-02-09 22:01:15 UTC
Description of problem:
When you do an OCP deployment with gluster for storage, you will get the following error in the ansible.log on the fusor server if you specified
a FQDN for the address of the gluster server:

7-02-09 16:29:28,029 p=14510 u=foreman | fatal: [rootofweevils-ocp-master1.b.b]: FAILED! => {"changed": true, "cmd": ["oc", "create", "-f", "/home/cloudsuite-install/pod_examples/glusterfs-endpoints.yaml"], "delta": "0:00:00.246671", "end": "2017-02-09 16:29:25.767250", "failed": true, "rc": 1, "start": "2017-02-09 16:29:25.520579", "stderr": "The Endpoints \"glusterfs-cluster\" is invalid.\nsubsets[0].addresses[0].ip: Invalid value: \"gluster.b.b\": must be a valid IP address", "stdout": "", "stdout_lines": [], "warnings": []}

On a hunch from Landon I checked to see if you ran the command with the IP address in the yaml file rather than with FQDN, if it would succeed and it did.

I personally think this is a bug in the "oc create" command because it should be able to handle a resolvable DNS address, however short term it may be better to just make sure the YAML file gets the IP address rather than the DNS address.

The failure is at 90%

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

How reproducible:
Every time

Steps to Reproduce:
1.  Do an OCP deployment with gluster and specify the FQDN for the address
    of the gluster server.

Actual results:
It fails at 90% with the above error.

Expected results:
No failure.

Comment 1 John Matthews 2017-02-10 17:10:03 UTC
According to below link OCP requires IP's and not hostnames with gluster.


"The ip values must be the actual IP addresses of a Gluster server, not fully-qualified host names"

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