[Flaky test] gce-master-scale-correctness

[gracenng]

Which jobs are failing flaky?

master-informing
gce-master-scale-correctness

Which tests are failing?

Kubernetes e2e suite: [It] [sig-network] LoadBalancers should not have connectivity disruption during rolling update with externalTrafficPolicy=Cluster

Since when has it been failing?

01-26 04:01 PST

Testgrid link

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

Reason for failure (if possible)

{ failed [FAILED] error waiting for daemon pods to be ready: timed out waiting for the condition
In [It] at: test/e2e/network/loadbalancer.go:1865 @ 01/27/23 13:45:59.532
}

Anything else we need to know?

No response

Relevant SIG(s)

/sig-scalability

cc @Laura

[aojea]

/assign
/cc @andrewsykim

I warned this test was going to flake ;)

[aojea]

/sig network

[gracenng]

Currently flaky so I updated the title but will keep issue open until further stability

[aojea]

yes, agreed

[aojea]

one failure is a GCE problem
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scale-correctness/1618579963147980800

{ failed [FAILED] timed out waiting for service "test-lb-rolling-update" to have a load balancer: timed out waiting for the condition

the other a deployment problem
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scale-correctness/1618942354264166400

{ failed [FAILED] error waiting for daemon pods to be ready: timed out waiting for the condition
In [It] at: test/e2e/network/loadbalancer.go:1865 @ 01/27/23 13:45:59.532

Failures look environmental, but let's keep it open until we get 5/5 greens on this test, there may be a symptom of a regression somewhere else

[shaneutt]

As per discussion of this issue in the SIG Network meeting today, marking this one as accepted.

/triage accepted

[k8s-ci-robot]

@drewhagen: The label(s) /label kind/flake cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, official-cve-feed. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label kind/flake

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

@drewhagen: The label(s) /label flake cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, official-cve-feed. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label flake

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[drewhagen]

/kind flake

[drewhagen]

/remove-kind failing-test

[aojea]

/assign

it fails with

{ failed [FAILED] error waiting for daemon pods to start: timed out waiting for the condition

we need to cap it for large clusters