此内容没有您所选择的语言版本。
3.4. DNS Propagation Fails when Creating an Application
Creating an application can fail if the application's hostname cannot be resolved. This problem typically occurs if a client host in an OpenShift Enterprise deployment does not have the broker host correctly configured as a nameserver, either directly or through delegation. An example of such a failure is shown in the following sample screen output:
Eventually the process will timeout while attempting to resolve the application's hostname.
$ rhc app create -a myapp -t jbossas-7
Creating application: myapp in domain
Now your new domain name is being propagated (this might take a minute)...
........
retry # 3 - Waiting for DNS: myapp-domain.example.com
This issue can indicate that broker DNS updates are failing, or that the client host does not have the correct nameserver configured to receive DNS updates from the broker host.
This problem can also occur if the
PUBLIC_HOSTNAME setting in the /etc/openshift/node.conf file on the node host is incorrectly configured.
Note
The
oo-admin-chk script on the broker host can help detect this problem.