openshift-ansible: Openshift Origin 3.9 Install Failure - origin-master-api restart failure

Description

On a single node install (and single master multiple node) of origin using awx, the install fails with the message:

Unable to restart service origin-master-api: Job for origin-master-api.service failed because the control process exited with error code. See "systemctl status origin-master-api.service" and "journalctl -xe" for details.

Version

Ansible Version (running inside awx_task container)

ansible 2.5.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, Aug  4 2017, 00:39:18) [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)]

Git Describe

openshift-ansible-3.9.29-1-28-gdbfbb5b47

Steps To Reproduce

1. Fresh install of CentOS 7 Minimal W/ pass-wordless sudo and ssh key (machine credential within AWX)
2. run the prerequisites playbook
3. run the deploy_cluster playbook

Expected Results

Openshift should install successfully

Observed Results

An error occurs at Play 36, Task 510

{
    "_ansible_parsed": true,
    "_ansible_no_log": false,
    "_ansible_notify": [
        "Verify API Server"
    ],
    "changed": false,
    "invocation": {
        "module_args": {
            "no_block": false,
            "name": "origin-master-api",
            "enabled": null,
            "daemon_reload": false,
            "state": "restarted",
            "user": false,
            "masked": null
        }
    },
    "msg": "Unable to restart service origin-master-api: Job for origin-master-api.service failed because the control process exited with error code. See \"systemctl status origin-master-api.service\" and \"journalctl -xe\" for details.\n"
}

Running the above systemctl command gives:

origin-master-api.service - Atomic OpenShift Master API
   Loaded: loaded (/usr/lib/systemd/system/origin-master-api.service; enabled; vendor preset: disabled)
   Active: activating (start) since Tue 2018-05-15 20:50:07 AWST; 18s ago
     Docs: https://github.com/openshift/origin
 Main PID: 8372 (openshift)
   CGroup: /system.slice/origin-master-api.service
           └─8372 /usr/bin/openshift start master api --config=/etc/origin/master/master-config.yaml --loglevel=2 --listen=https://0.0.0.0:8443 --master=https://bcvosm01d.domain.net:8443

May 15 20:50:07 bcvosm01d.domain.net atomic-openshift-master-api[8372]: I0515 20:50:07.905419    8372 plugins.go:83] Registered admission plugin "SecurityContextDeny"
May 15 20:50:07 bcvosm01d.domain.net atomic-openshift-master-api[8372]: I0515 20:50:07.905426    8372 plugins.go:83] Registered admission plugin "ServiceAccount"
May 15 20:50:07 bcvosm01d.domain.net atomic-openshift-master-api[8372]: I0515 20:50:07.905431    8372 plugins.go:83] Registered admission plugin "DefaultStorageClass"
May 15 20:50:07 bcvosm01d.domain.net atomic-openshift-master-api[8372]: I0515 20:50:07.905437    8372 plugins.go:83] Registered admission plugin "PersistentVolumeClaimResize"
May 15 20:50:07 bcvosm01d.domain.net atomic-openshift-master-api[8372]: I0515 20:50:07.905442    8372 plugins.go:83] Registered admission plugin "PVCProtection"
May 15 20:50:08 bcvosm01d.domain.net atomic-openshift-master-api[8372]: I0515 20:50:08.155644    8372 master_config.go:445] Initializing cache sizes based on 0MB limit
May 15 20:50:08 bcvosm01d.domain.net atomic-openshift-master-api[8372]: I0515 20:50:08.155740    8372 master_config.go:509] Using the lease endpoint reconciler with TTL=15s and interval=10s
May 15 20:50:08 bcvosm01d.domain.net atomic-openshift-master-api[8372]: I0515 20:50:08.159157    8372 start_master.go:558] Starting master on 0.0.0.0:8443 (v3.9.0+ba7faec-1)
May 15 20:50:08 bcvosm01d.domain.net atomic-openshift-master-api[8372]: I0515 20:50:08.159173    8372 start_master.go:559] Public master address is https://bcvosm01d.domain.net:8443
May 15 20:50:08 bcvosm01d.domain.net atomic-openshift-master-api[8372]: I0515 20:50:08.159187    8372 start_master.go:566] Using images from "openshift/origin-<component>:v3.9.0"

Trying to manually restart gives the same prompt as before

Restarting the host gives:

origin-master-api.service - Atomic OpenShift Master API
   Loaded: loaded (/usr/lib/systemd/system/origin-master-api.service; enabled; vendor preset: disabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2018-05-15 22:22:39 AWST; 2s ago
     Docs: https://github.com/openshift/origin
  Process: 1602 ExecStart=/usr/bin/openshift start master api --config=${CONFIG_FILE} $OPTIONS (code=exited, status=255)
 Main PID: 1602 (code=exited, status=255)

May 15 22:22:39 bcvosm01d.domain.net systemd[1]: Failed to start Atomic OpenShift Master API.
May 15 22:22:39 bcvosm01d.domain.net systemd[1]: Unit origin-master-api.service entered failed state.
May 15 22:22:39 bcvosm01d.domain.net systemd[1]: origin-master-api.service failed.

Additional Information

I’ve been trying this over several days (more like two weeks) with various iterations. Two master cluster with onboard etcd and 3 nodes, Single master, 3 nodes. Single node (master, etcd and node) only.

All of the above methods resulted in the same error.

Have also tried installing on atomic hosts (which is how i eventually want it to be) This caused errors downloading containers, though that is a separate issue entirely and ill cross that bridge when i get to it.

OS: CentOS 7 Minimal (Latest Updates) running inside Vmware VM W/ 75GB HDD and 16Gb RAM

AWX Template Vars

openshift_deployment_type: origin
openshift_enable_excluders: False
ansible_become: yes
openshift_release: 3.9.0
deprecation_warnings: False
openshift_disable_check: memory_availability
openshift_image_tag: v3.9.0
openshift_pkg_version: -3.9.0
openshift_clock_enabled: True