+++ This bug was initially created as a clone of Bug #1613546 +++ Description of problem: In azure the load balancer svc cannot be created due to missing configuration parameters. Version-Release number of selected component (if applicable): atomic-openshift-excluder-3.10.14-1.git.0.ba8ae6d.el7.noarch atomic-openshift-hyperkube-3.10.14-1.git.0.ba8ae6d.el7.x86_64 atomic-openshift-node-3.10.14-1.git.0.ba8ae6d.el7.x86_64 atomic-openshift-clients-3.10.14-1.git.0.ba8ae6d.el7.x86_64 atomic-openshift-docker-excluder-3.10.14-1.git.0.ba8ae6d.el7.noarch atomic-openshift-3.10.14-1.git.0.ba8ae6d.el7.x86_64 How reproducible: Perform the installation with the the following parameters in the inventory as they relate to your environment #310 openshift_cloudprovider_kind=azure openshift_cloudprovider_azure_client_id=ID openshift_cloudprovider_azure_client_secret=SECRET openshift_cloudprovider_azure_tenant_id=TENANT openshift_cloudprovider_azure_subscription_id=SUB openshift_cloudprovider_azure_resource_group=refarch-azr openshift_cloudprovider_azure_location=eastus openshift_release=v3.10 #310end Steps to Reproduce: 1. deploy 3.10 with the above values 2. create a load balancer svc vi load.yaml apiVersion: v1 kind: Service metadata: name: egress-21 spec: ports: - name: web port: 8080 type: LoadBalancer selector: deploymentconfig: app oc create -f load.yaml Actual results: load balancer stays in pending state egress-21 LoadBalancer 172.30.245.15 <pending> 8080:32566/TCP 7m Expected results: egress-21 LoadBalancer 172.30.245.15 137.117.45.245 8080:32566/TCP 7m Additional info: The required values are actually located here https://docs.openshift.com/container-platform/3.10/install_config/configuring_azure.html#azure-configuration-file Description of problem: Version-Release number of the following components: rpm -q openshift-ansible rpm -q ansible ansible --version How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Please include the entire output from the last TASK line through the end of output if an error is generated Expected results: Additional info: Please attach logs from ansible-playbook with the -vvv flag --- Additional comment from Ryan Cook on 2018-08-07 16:23:14 EDT --- TESTING https://github.com/openshift/openshift-ansible/pull/9473 --- Additional comment from Ryan Cook on 2018-08-09 10:07:27 EDT --- The PR does the needful
https://github.com/openshift/openshift-ansible/pull/9558 3.10 backport
(In reply to Scott Dodson from comment #1) > https://github.com/openshift/openshift-ansible/pull/9558 3.10 backport @Scott Would you mind backport this one [1] to 3.10 as well? [1]. https://github.com/openshift/openshift-ansible/pull/9789
Looks like there is a backport: https://github.com/openshift/openshift-ansible/pull/9818
Checked with version openshift-ansible-3.10.35-1.git.0.e5b821eNone.noarch, the latest PR doesn't merged. Related PR merged in openshift-ansible-3.10.42-1
Verified with version openshift-ansible-3.10.43-1.git.0.4794155.el7.noarch, code has been merged in this version. Installation is good now.
*** Bug 1627971 has been marked as a duplicate of this bug. ***
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:2695