Bug 1776672
| Summary: | Creation of ingress controller of LoadBalancerService type is failing on Azure | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Arnab Ghosh <arghosh> | ||||
| Component: | Networking | Assignee: | Dan Mace <dmace> | ||||
| Networking sub component: | router | QA Contact: | Hongan Li <hongli> | ||||
| Status: | CLOSED DUPLICATE | Docs Contact: | |||||
| Severity: | medium | ||||||
| Priority: | unspecified | CC: | aos-bugs, bbennett, mmasters | ||||
| Version: | 4.2.z | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.3.0 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-12-03 13:54:44 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
This looks like it may be a duplicate of bug 1763727. @Miciah, Yes, the issue in both bugzillas are same *** This bug has been marked as a duplicate of bug 1763727 *** |
Created attachment 1639699 [details] Events log Description of problem: Facing issue while publishing Ingress Controllers with internal cloud load balancers. Here Azure public cloud provider is being used. Could see following error in event log. ~~~ 4s Warning CreatingLoadBalancerFailed service/router-default Error creating load balancer (will retry): failed to ensure load balancer for service openshift-ingress/router-default: ensure(openshift-ingress/router-default): lb(ocpmain-vxxxl-internal) - failed to get subnet: ocpmain-vxxxl-vnet/ocpmain-vxxxl-node-subnet ~~~ The Ingress controller definition looks like below. ~~~ apiVersion: operator.openshift.io/v1 kind: IngressController metadata: name: default namespace: openshift-ingress-operator spec: defaultCertificate: name: tls-my-domain endpointPublishingStrategy: loadBalancer: scope: Internal type: LoadBalancerService nodePlacement: nodeSelector: matchLabels: node-role.kubernetes.io/infra: '' replicas: 2 ~~~ Could create ingress controller of type LoadBalancerService in AWS using same definition. Version-Release number of selected component (if applicable): Openshift 4.2 How reproducible: Not Sure Steps to Reproduce: 1. 2. 3. Actual results: Load balancer is not being created Expected results: A new private load balancer should be created on Azure and act as an Ingress controller Additional info: