-
Bug
-
Resolution: Done-Errata
-
Major
-
4.14
-
None
-
No
-
CLOUD Sprint 243
-
1
-
Approved
-
False
-
-
N/A
-
Release Note Not Required
This is a clone of issue OCPBUGS-18841. The following is the description of the original issue:
—
Description of problem:
Failed to run auto OCP-57089 on a 4.14 azure platform, manually checked it, the created load-balancer service couldn't get an external-IP address
Version-Release number of selected component (if applicable):
4.14.0-0.nightly-2023-09-09-164123
How reproducible:
100% on the cluster
Steps to Reproduce:
1. Add a wait in the auto script, then run the case g.By("check if the lb services have obtained the EXTERNAL-IPs") regExp := "([0-9]+.[0-9]+.[0-9]+.[0-9]+)" time.Sleep(3600 * time.Second) % ./bin/extended-platform-tests run all --dry-run | grep 57089 | ./bin/extended-platform-tests run -f - 2. % oc get ns | grep e2e-test-router e2e-test-router-ingressclass-n2z2c Active 2m51s 3. It was pending in EXTERNAL-IP column for internal-lb-57089 service % oc -n e2e-test-router-ingressclass-n2z2c get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE external-lb-57089 LoadBalancer 172.30.198.7 20.42.34.61 28443:30193/TCP 3m6s internal-lb-57089 LoadBalancer 172.30.214.30 <pending> 29443:31507/TCP 3m6s service-secure ClusterIP 172.30.47.70 <none> 27443/TCP 3m13s service-unsecure ClusterIP 172.30.175.59 <none> 27017/TCP 3m13s % 4. % oc -n e2e-test-router-ingressclass-n2z2c get svc internal-lb-57089 -oyaml apiVersion: v1 kind: Service metadata: annotations: service.beta.kubernetes.io/azure-load-balancer-internal: "true" creationTimestamp: "2023-09-12T07:56:42Z" finalizers: - service.kubernetes.io/load-balancer-cleanup name: internal-lb-57089 namespace: e2e-test-router-ingressclass-n2z2c resourceVersion: "209376" uid: b163bc03-b1c6-4e7b-b4e1-c996e9d135f4 spec: allocateLoadBalancerNodePorts: true clusterIP: 172.30.214.30 clusterIPs: - 172.30.214.30 externalTrafficPolicy: Cluster internalTrafficPolicy: Cluster ipFamilies: - IPv4 ipFamilyPolicy: SingleStack ports: - name: https nodePort: 31507 port: 29443 protocol: TCP targetPort: 8443 selector: name: web-server-rc sessionAffinity: None type: LoadBalancer status: loadBalancer: {} %
Actual results:
internal-lb-57089 service couldn't get an external-IP address
Expected results:
internal-lb-57089 service can get an external-IP address
Additional info:
- clones
-
OCPBUGS-18841 OCP-57089 and OCP-24504 failed in 4.14 azure platform for the load-balancer service couldn't get an external-IP address
- Closed
- is blocked by
-
OCPBUGS-18841 OCP-57089 and OCP-24504 failed in 4.14 azure platform for the load-balancer service couldn't get an external-IP address
- Closed
- is related to
-
OCPSTRAT-513 Azure managed identity with Azure AD workload identity for self-managed OpenShift
- Closed
- links to
-
RHSA-2023:5006 OpenShift Container Platform 4.14.z security update