openshift-ansible: Openshift Origin 3.7 FAILED - RETRYING: wait for api server to be ready

Description

During the installation of Openshift Origin the playbook fails on this step:

FAILED - RETRYING: wait for api server to be ready (120 retries left).

The problem seems to be related with service catalog present on the newer Openshift Origin version.

Version

# ansible --version
ansible 2.4.1.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 = /bin/ansible
  python version = 2.7.5 (default, May  3 2017, 07:55:04) [GCC 4.8.5 20150623 (Red Hat 4.8.5-14)]
# git describe
openshift-ansible-3.7.11-1-15-g31d3bb3

Steps To Reproduce

Download the latest version of openshift-ansible and use branch release-3.7
Execute the config.yml playbook to install the newer version of OSE

Expected Results

The playbook execution with the error on the service catalog test.

Observed Results

The deployment fails the execution with the version 3.7.0 but it works on 3.6.1 with the specific playbook used from openshift-ansible

Additional Information

# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.4 (Maipo)

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 15 (2 by maintainers)

Most upvoted comments

I rebooted my master, and the nodes, and now the oc commands return right away, because at the summary at the end it said:

	This phase can be restarted by running: playbooks/byo/openshift-cluster/service-catalog.yml

I attempted to do that, and things went a lot faster, but I’m still getting back to the

FAILED - RETRYING: wait for api server to be ready (120 retries left).

If I try to do the curl command manually:

curl -k https://apiserver.kube-service-catalog.svc/healthz
curl: (6) Could not resolve host: apiserver.kube-service-catalog.svc; Name or service not known

micah on Dec 6, 2017