Description of problem: In this section, we tell people they can put entries in /etc/hosts on their workstation in order to test the server. This won't really work very well. They can create the entries enough to use the broker but they'll have to keep creating entries for each app they create, and that is not really the experience we want them to have. Also we should be clear that this is just for testing. For a real installation the organization's DNS servers need to know how to handle OpenShift DNS. In fact all of section 8 kind of needs to make that clear, but let's just stick with this part. Actual results: You need to configure developer workstations to resolve the host names used in your OpenShift Enterprise deployment. There are three ways to do this: > Edit the /etc/resolv.conf file to use a DNS server that can resolve the addresses used for the broker and any applications on your OpenShift Enterprise deployment. > Add the required addresses to the /etc/hosts file on the workstation. > Use the OpenShift client tools directly on the broker. Expected results: You need to configure developer workstations to resolve the host names used in your OpenShift Enterprise deployment. There are two ways to do this simply for testing purposes: > Edit the client host's /etc/resolv.conf file to add the DNS server from your OpenShift Enterprise deployment to the top. > Install and use the OpenShift client tools inside the installation (for convenience, the kickstart script installs them when installing the broker). Additional info:
This will be fixed/updated in the next release.
Correction: for comment #3, it should be Section 8.4 of the doc.
These are released AFAIK, apparently not in the errata release.