Bug 1127321 - When using OSE with your own domain name (example.com for example) RHC tools does not respect resolver on OSX
Summary: When using OSE with your own domain name (example.com for example) RHC tools ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
medium
urgent
Target Milestone: ---
: ---
Assignee: Miciah Dashiel Butler Masters
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-06 16:10 UTC by Grant Shipley
Modified: 2017-01-13 22:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-13 22:03:19 UTC


Attachments (Terms of Use)

Description Grant Shipley 2014-08-06 16:10:45 UTC
Description of problem:
When installing and using OSE 2.1 with a full install or via virtual machine, the RHC client tools installed on a users local machine does not respect the /etc/resolver dns resolution on OSX.


Version-Release number of selected component (if applicable):
rhc-1.28.5.gem
OSE 2.1 VM

How reproducible:
Always

Steps to Reproduce:
1. Run the OSE2.1 Virtual Machine
2. Install the client tools on an OSX machine
3. As the root user on OSX, create the following:
mkdir /etc/resolver
vi /etc/resolver/example.com

Place the following contents in the resolver file:
domain example.com
nameserver 192.168.0.24

Ensure to replace the 192.168.0.24 with the correct IP for your OSE DNS server.

4. Run: rhc setup --server vm.openshift.example.com -l demo -p openshift
5. rhc app create testapp php-5.4
6. See the following error

Application Options
-------------------
Domain:     ose
Cartridges: php-5.4
Gear Size:  default
Scaling:    no

Creating application 'l4' ... done


Waiting for your DNS name to be available ...     retry # 1 - Waiting for DNS: l4-ose.openshift.example.com
    retry # 2 - Waiting for DNS: l4-ose.openshift.example.com
    retry # 3 - Waiting for DNS: l4-ose.openshift.example.com
    retry # 4 - Waiting for DNS: l4-ose.openshift.example.com
    retry # 5 - Waiting for DNS: l4-ose.openshift.example.com
    retry # 6 - Waiting for DNS: l4-ose.openshift.example.com

At the same time, open a new window and ping the newly created application:
$ ping l4-ose.openshift.example.com
PING vm.openshift.example.com (192.168.0.24): 56 data bytes
64 bytes from 192.168.0.24: icmp_seq=0 ttl=64 time=0.188 ms

The application is also available via web browser from the OSX system.

This is a problem with RHC connecting to OSE using a custom dns host.  The eclipse plugin does not have this problem running on the same machine which makes me think it is how the ruby library we are using resolves host names.

Actual results:
RHC client tools do not use / respect the /etc/resolver system on OSX.

Expected results:
RHC should respect this system like all of the other tools (Eclipse, IntelliJ etc)

Additional info:

Comment 2 Rory Thrasher 2017-01-13 22:03:19 UTC
OpenShift Enterprise v2 has officially reached EoL.  This product is no longer supported and bugs will be closed.

Please look into the replacement enterprise-grade container option, OpenShift Container Platform v3.  https://www.openshift.com/container-platform/

More information can be found here: https://access.redhat.com/support/policy/updates/openshift/


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