Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure cluster [c1aa76ec...] e2e-ci-kubernetes-e2e-al2023-aws-conformance-aws-cni and ci-kubernetes-e2e-al2023-aws-conformance-canary are broken #16938

Open
dims opened this issue Nov 9, 2024 · 6 comments
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@k8s-ci-robot k8s-ci-robot added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Nov 9, 2024
@k8s-ci-robot
Copy link
Contributor

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Nov 9, 2024
@k8s-ci-robot
Copy link
Contributor

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Nov 9, 2024
@dims
Copy link
Member Author

dims commented Nov 9, 2024

Looks like we have one more bucket related issue.

I1108 21:20:13.948454   15644 subnets.go:224] Assigned CIDR 172.20.0.0/16 to subnet ap-northeast-2a
Error: error building complete spec: failed to get bucket details for "s3://k8s-kops-ci-prow/discovery/kubernetes-e2e-al2023-aws-conformance-aws-cni.k8s.local": Could not retrieve location for AWS bucket k8s-kops-ci-prow
W1108 21:20:19.544288   15580 state.go:46] failed to run /home/prow/go/src/k8s.io/kops/_rundir/722adbc3-f9a4-4b30-bd17-795eb653a71f/kops get cluster kubernetes-e2e-al2023-aws-conformance-aws-cni.k8s.local -ojson; stderr=Error: cluster not found "kubernetes-e2e-al2023-aws-conformance-aws-cni.k8s.local"
Error: exit status 1

@dims
Copy link
Member Author

dims commented Nov 9, 2024

/transfer kops

@k8s-ci-robot k8s-ci-robot transferred this issue from kubernetes/kubernetes Nov 9, 2024
@dims
Copy link
Member Author

dims commented Nov 9, 2024

cc @rifelpet @hakman

@hakman
Copy link
Member

hakman commented Nov 10, 2024

Planning to look at this when back from KubeCon, unless @rifelpet beats me to it. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

3 participants