Failure cluster [c1aa76ec...] AWS kops tests failing with `Could not retrieve location for AWS bucket k8s-kops-ci-prow`

[dims]

Failure cluster c1aa76ec7c67c92366fc

Error text:

exit status 1

Log Snippet:

Error: error building complete spec: failed to get bucket details for "s3://k8s-kops-ci-prow/discovery/e2e-e2e-ci-kubernetes-e2e-al2023-aws-alpha-features.test-cncf-aws.k8s.io": Could not retrieve location for AWS bucket k8s-kops-ci-prow
W1024 07:22:43.126256   15131 state.go:46] failed to run /home/prow/go/src/k8s.io/kops/_rundir/32aa84fc-036f-4df0-a6df-c48882dc07cb/kops get cluster e2e-e2e-ci-kubernetes-e2e-al2023-aws-alpha-features.test-cncf-aws.k8s.io -ojson; stderr=Error: cluster not found "e2e-e2e-ci-kubernetes-e2e-al2023-aws-alpha-features.test-cncf-aws.k8s.io"
Error: exit status 1

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

[k8s-ci-robot]

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.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[k8s-ci-robot]

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.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[dims]

/transfer kops

[dims]

@rifelpet do we need to revert discovery store migration for these too? https://github.com/kubernetes/test-infra/pull/33597

[ameukam]

Not really. Looks like they run on the wrong cluster. Should be k8s-infra-kops-prow-build

[dims]

ACK, will file a PR in test-infra @ameukam

[dims]

Hmm some are in "eks-prow-build-cluster" and others are in "k8s-infra-prow-build" ... will leave this to the experts :)