-
Notifications
You must be signed in to change notification settings - Fork 635
Closed
Labels
area/provider/eksIssues or PRs related to Amazon EKS providerIssues or PRs related to Amazon EKS providerarea/testingIssues or PRs related to testingIssues or PRs related to testingkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/activeIndicates that an issue or PR is actively being worked on by a contributor.Indicates that an issue or PR is actively being worked on by a contributor.needs-priorityneeds-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.
Description
/kind bug
/area provider/eks
/area testing
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
The EKS e2e tests are consistently failing on this test case:
capa-eks-e2e: [It] [managed] [general] [ipv6] EKS cluster tests should create a cluster and add nodes
What did you expect to happen:
e2e should continue passing.
Anything else you would like to add:
Last passing test: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_cluster-api-provider-aws/5498/pull-cluster-api-provider-aws-e2e-eks/1927445735872139264
Environment:
- Cluster-api-provider-aws version: main
Metadata
Metadata
Assignees
Labels
area/provider/eksIssues or PRs related to Amazon EKS providerIssues or PRs related to Amazon EKS providerarea/testingIssues or PRs related to testingIssues or PRs related to testingkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/activeIndicates that an issue or PR is actively being worked on by a contributor.Indicates that an issue or PR is actively being worked on by a contributor.needs-priorityneeds-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.
Type
Projects
Status
Done