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

Look into Failure for Cluster Teardown #1797

Open
kensipe opened this issue May 14, 2021 · 1 comment
Open

Look into Failure for Cluster Teardown #1797

kensipe opened this issue May 14, 2021 · 1 comment

Comments

@kensipe
Copy link
Member

kensipe commented May 14, 2021

A KEP PR resulting in a test failure... it is a failure for waiting for teardown. We should understand if this failure is a concern and consider removing it as a test result if we do not care.

harness.go:579: fatal error running commands: command "./bin/kubectl-kudo init --unsafe-self-signed-webhook-ca --kudo-image kudobuilder/controller:test --kudo-image-pull-policy Never --wait" exceeded 300 sec timeout

From: #1794

What would you like to be added:

Why is this needed:

@asekretenko
Copy link
Member

asekretenko commented May 14, 2021

@kensipe Is this really a teardown failure?..

From what I could see in the logs, this is a failure of waiting for kudo to be installed, and it looks like kudo controller manager pod has never been scheduled in this run.

Something very similar is observed in upgrade tests on a much more regular basis, see #1783

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants