Closed frippe75 closed 5 years ago
I re-ran the ansible playbook for the 40-th time. And now it passed this step and almost finnished. Could be that I'm resource starved or something around my networking/proxy. docker pull's have been ridicously slow (in segmented lab-network-type-of-setup).
My Openstack env consists of a single controller-node and three compute nodes each having 96GB mem and 12 core each. m1.medium is the recommended flavor to use and mine is the default one. So I should have resources available to be successful...
Description
Service Catalog install failed.
Seeing the same as in #10819 but my issue (from what I can tell) is not caused by the incorrect wildcard DNS entry as he had.
But other similarities are that we were both running non-co-located etcd and masters.
openshift_openstack_num_masters: 3 openshift_openstack_num_infra: 1 openshift_openstack_num_cns: 0 openshift_openstack_num_nodes: 3 openshift_openstack_num_etcd: 3
I'm running using the Openstack playbook and using CentOS 7.5.1804. On Openstack Rocky release. Also running behind a squid proxy. Using a single MS DNS server setting -pub as a name suffix for floating ip's. I.e master-0-pub.os.lab.net for the floating IP's and master-0.os.lab.net for internal addresses.
Version
Steps To Reproduce
ansible-playbook --user openshift \ -vvvv \ -i openshift-ansible/playbooks/openstack/inventory.py \ -i inventory \ openshift-ansible/playbooks/openstack/openshift-cluster/provision_install.yml
Expected Results
Getting OKD 3.11 provisioned
Observed Results
And... The actual wait for the roll-out was like an hour.
The actual fail in detail...
Additional Information