origin: OCP v3.9.0-0.53.0 "oc cluster up" never finishes

Attempt to start cluster with oc cluster up with OCP oc and image never finishes.

Version

[provide output of the openshift version or oc version command]

oc v3.9.0-0.53.0
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth GSSAPI Kerberos SPNEGO

Steps To Reproduce

1. Configure 3.9 repo.
2. yum install /usr/bin/oc
3. Log in to registry.reg-aws.openshift.com.
4. docker pull registry.reg-aws.openshift.com/openshift3/ose:v3.9.0-0.53.0
5. oc cluster up '--image=registry.reg-aws.openshift.com/openshift3/ose'

Current Result

Using nsenter mounter for OpenShift volumes
Using 127.0.0.1 as the server IP
Starting OpenShift using registry.reg-aws.openshift.com/openshift3/ose:v3.9.0-0.53.0 ...

Expected Result

Output similar to what I get with OCP 3.7:

Starting OpenShift using registry.access.redhat.com/openshift3/ose:v3.7.31 ...
OpenShift server started.

The server is accessible via web console at:
    https://127.0.0.1:8443

You are logged in as:
    User:     developer
    Password: <any value>

To login as administrator:
    oc login -u system:admin

and the oc cluster up command finishing, putting me back to the terminal.

Additional Information

[try to run $ oc adm diagnostics (or oadm diagnostics) command if possible] [if you are reporting issue related to builds, provide build logs with BUILD_LOGLEVEL=5] [consider attaching output of the $ oc get all -o json -n <namespace> command to the issue] [visit https://docs.openshift.org/latest/welcome/index.html]

This is both on RHEL 7.4 and RHEL 7.5 nightly.