Open dims opened 1 day ago
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
/sig <group-name>
/wg <group-name>
/committee <group-name>
Please see the group list for a listing of the SIGs, working groups, and committees available.
This issue is currently awaiting triage.
If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
/transfer kops
@rifelpet do we need to revert discovery store migration for these too? https://github.com/kubernetes/test-infra/pull/33597
Not really. Looks like they run on the wrong cluster. Should be k8s-infra-kops-prow-build
ACK, will file a PR in test-infra @ameukam
Hmm some are in "eks-prow-build-cluster" and others are in "k8s-infra-prow-build" ... will leave this to the experts :)
Failure cluster c1aa76ec7c67c92366fc
Error text:
Log Snippet:
Recent failures:
10/24/2024, 3:18:05 AM e2e-ci-kubernetes-e2e-al2023-aws-alpha-features 10/24/2024, 2:58:12 AM e2e-ci-kubernetes-e2e-al2023-aws-disruptive-canary 10/24/2024, 2:23:10 AM e2e-ci-kubernetes-e2e-al2023-aws-slow-canary 10/24/2024, 2:11:05 AM e2e-ci-kubernetes-e2e-al2023-aws-conformance-aws-cni-canary 10/24/2024, 2:07:17 AM e2e-ci-kubernetes-e2e-al2023-aws-serial-canary
/kind failing-test