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.

Sign up for GitHub

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

Jump to bottom

Timed out after 300.000s. Timed out waiting for all machines to be exist #9886

Closed
adilGhaffarDev opened this issue Dec 16, 2023 · 1 comment · Fixed by #9892
Closed

Timed out after 300.000s. Timed out waiting for all machines to be exist #9886

adilGhaffarDev opened this issue Dec 16, 2023 · 1 comment · Fixed by #9892
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@adilGhaffarDev
Copy link
Contributor

adilGhaffarDev commented Dec 16, 2023 •
edited

Which jobs are failing?

Failing:

  • capi-e2e-dualstack-and-ipv6-main

Flaking:

  • capi-e2e-main
  • capi-e2e-mink8s-main

Which tests are failing?

capi-e2e: [It] When testing clusterctl upgrades using ClusterClass (v1.6=>current) [ClusterClass] Should create a management cluster and then upgrade all the providers

Since when has it been failing?

this fail started happening after the merge of this PR: #9799

Testgrid link

https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api#capi-e2e-dualstack-and-ipv6-main
https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api#capi-e2e-main
https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api#capi-e2e-mink8s-main

Reason for failure (if possible)

need to investigate.

Anything else we need to know?

No response

Label(s) to be applied

/kind failing-test
@k8s-ci-robot k8s-ci-robot added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 16, 2023
@killianmuldoon
Copy link
Contributor

/triage accepted

Looks like this test is very very flaky, but not permafailing. Would be great to find the root cause soon.

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 17, 2023
@adilGhaffarDev adilGhaffarDev mentioned this issue Dec 18, 2023
Closed
@sbueringer sbueringer mentioned this issue Dec 18, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

🐛 test/e2e: Calculate correct worker count in clusterctl upgrade test sbueringer/cluster-api
3 participants
@k8s-ci-robot @adilGhaffarDev @killianmuldoon