Description of problem: After installation of OpenStack 14 and OpenShift 3.11 docker-registry-1-deploy and router-1-deploy pods are in error state. Version-Release number of the following components: openshift-ansible-3.11.23-1.git.0.19cbe21.el7.noarch ansible-2.6.5-1.el7ae.noarch ansible 2.6.5 How reproducible: Steps to Reproduce: 1. Install OSP 14 2. Run Openstack playbooks: $ ansible-playbook --user openshift -i "/usr/share/ansible/openshift-ansible/playbooks/openstack/inventory.py" -i inventory "/usr/share/ansible/openshift-ansible/playbooks/openstack/openshift-cluster/prerequisites.yml" $ ansible-playbook --user openshift -i "/usr/share/ansible/openshift-ansible/playbooks/openstack/inventory.py" -i inventory "/usr/share/ansible/openshift-ansible/playbooks/openstack/openshift-cluster/provision.yml" $ ansible-playbook --user openshift -i "/usr/share/ansible/openshift-ansible/playbooks/openstack/inventory.py" -i inventory red-hat-ca.yml $ ansible-playbook --user openshift -i "/usr/share/ansible/openshift-ansible/playbooks/openstack/inventory.py" -i inventory repos.yml $ ansible-playbook --user openshift -i "/usr/share/ansible/openshift-ansible/playbooks/openstack/inventory.py" -i inventory "/usr/share/ansible/openshift-ansible/playbooks/openstack/openshift-cluster/install.yml" Actual results: Expected results: Additional info:
This is related to the Octavia LoadBalancer listeners timeouts used for accessing the OpenShift API. I created the next PR to increase that value to 500 seconds instead of 50 seconds: https://github.com/openshift/openshift-ansible/pull/10446/files
When applying the patch, After the installation is complete the registry-console-1-deploy is in ContainerCreating state for about 30-40 minutes.
Please help check if this bug could be verified,thanks!
Luis, Can you please update the fixed in version field?
Verified with: OSP14 openshift-ansible-3.11.41-1.git.0.f711b2d.el7.noarch
Verified
No pods in error state with: openshift-ansible-3.11.38-1.git.0.d146f83.el7.noarch (docker-registry- node-exporter are in ContainerCreating state)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3537