Bug 1420929
| Summary: | WebUI should warn if a hostname is entered for Gluster Endpoint during OCP deployment, hostnames are not supported by OCP for gluster. | |||
|---|---|---|---|---|
| Product: | Red Hat Quickstart Cloud Installer | Reporter: | James Olin Oden <joden> | |
| Component: | WebUI | Assignee: | John Matthews <jmatthew> | |
| Status: | NEW --- | QA Contact: | Sudhir Mallamprabhakara <smallamp> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 1.1 | CC: | bthurber, qci-bugzillas | |
| Target Milestone: | --- | Keywords: | Triaged | |
| Target Release: | 1.2 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1421239 (view as bug list) | Environment: | ||
| Last Closed: | 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: | 1421239 | |||
According to below link OCP requires IP's and not hostnames with gluster. https://docs.openshift.org/latest/install_config/persistent_storage/persistent_storage_glusterfs.html#creating-gluster-endpoints "The ip values must be the actual IP addresses of a Gluster server, not fully-qualified host names" |
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): QCI-1.1-RHEL-7-20170208.t.0 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.