Description of problem: Kuryr's loadbalancer service type support depends on the cloud provider running. When using Kuryr as sdn solution it is required to have 'openstack' as cloud provider, as described in [1]: kubernetesMasterConfig: ... apiServerArguments: cloud-provider: - "openstack" cloud-config: - "/etc/cloud.conf" controllerArguments: cloud-provider: - "openstack" cloud-config: - "/etc/cloud.conf" [1] https://docs.openshift.org/latest/install_config/configuring_openstack.html#openstack-configuring-masters-manually Version-Release number of the following components: $ rpm -q openshift-ansible openshift-ansible-3.10.0-0.67.0.git.107.1bd1f01.el7.noarch $ rpm -q ansible ansible-2.4.4.0-1.el7ae.noarch $ ansible --version ansible 2.4.4.0 config file = /etc/ansible/ansible.cfg configured module search path = [u'/home/cloud-user/.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, Feb 20 2018, 09:19:12) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)] How reproducible: 100% Steps to Reproduce: 1. Deploy OpenStack (OSP13) 2. Deploy a DNS server and the Ansible host in the overcloud 3. Download OCP rpm and configure: - OpenStack (inventory/group_vars/all.yml) . Configure Kuryr SDN - OpenShift (inventory/group_vars/OSEv3.yml) . Configure the Red Hat LDAP identity provider 4. Install OpenShift by running the playbooks for OpenStack (deployed 3 masters, 2 infra and 2 app nodes) and verify the installer succeeds without any errors. 5. Check '/etc/origin/master/master-config.yaml' file in master nodes Actual results: '/etc/origin/master/master-config.yaml' file does not contain the openstack cloud-provider as in: kubernetesMasterConfig: ... apiServerArguments: cloud-provider: - "openstack" cloud-config: - "/etc/cloud.conf" controllerArguments: cloud-provider: - "openstack" cloud-config: - "/etc/cloud.conf" Expected results: openstack cloud-provider should be configured
Hi Tzu-Mainn, this has already been handled long ago right? Can we close this bug?
Yep! We updated the documentation to clarify that kuryr required the use of the openstack cloud provider.