Skip to content

[Flaking Test] [sig-network] LoadBalancers tests fail with timeout waiting for service "xxx" to have a load balancer: context deadline exceeded #131863

@Rajalakshmi-Girish

Description

@Rajalakshmi-Girish

Which jobs are flaking?

sig-release-master-informing

  • gce-master-scale-correctness

https://prow.k8s.io/job-history/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gce-scale-correctness

Which tests are flaking?

[sig-network] LoadBalancers [Feature:LoadBalancer] should have session affinity work for LoadBalancer service with Local traffic policy [Slow] [LinuxOnly]
[sig-network] LoadBalancers [Feature:LoadBalancer] should handle load balancer cleanup finalizer for service [Slow]
[sig-network] LoadBalancers [Feature:LoadBalancer] should have session affinity work for LoadBalancer service with Cluster traffic policy [Slow] [LinuxOnly]
[sig-network] LoadBalancers [Feature:LoadBalancer] should be able to switch session affinity for LoadBalancer service with Cluster traffic policy [Slow] [LinuxOnly]
[sig-network] LoadBalancers [Feature:LoadBalancer] should be able to switch session affinity for LoadBalancer service with Local traffic policy [Slow] [LinuxOnly]
[sig-network] LoadBalancers ExternalTrafficPolicy: Local [Feature:LoadBalancer] [Slow] should only target nodes with endpoints

Since when has it been flaking?

5/16/2025, 10:31:32 PM
5/14/2025, 10:31:21 PM
5/6/2025, 10:31:14 PM

Testgrid link

https://testgrid.k8s.io/sig-release-master-informing#gce-master-scale-correctness

Reason for failure (if possible)

failed [FAILED] timed out waiting for service "xxx" to have a load balancer: context deadline exceeded

Anything else we need to know?

Old issue: #129839
Related issue in provider repo: kubernetes/cloud-provider-gcp#753
Ref slack threads: #sig-network: https://kubernetes.slack.com/archives/C09QYUH5W/p1714377706051539
#sig-release-ci-signal: https://kubernetes.slack.com/archives/CN0K3TE2C/p1737988381095549

Relevant SIG(s)

/sig network

Metadata

Metadata

Assignees

Labels

help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/flakeCategorizes issue or PR as related to a flaky test.sig/networkCategorizes an issue or PR as relevant to SIG Network.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

Status

FLAKY

Status

Tracked

Relationships

None yet

Development

No branches or pull requests

Issue actions