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

Refactor smoke tests #775

Open
jnummelin opened this issue Oct 14, 2024 · 1 comment · May be fixed by #845
Open

Refactor smoke tests #775

jnummelin opened this issue Oct 14, 2024 · 1 comment · May be fixed by #845
Assignees
Labels
keep Exempts issues and pull requests from stale workflow

Comments

@jnummelin
Copy link
Member

We need to refactor some/most of the smokes.

Duplication

There's lot of code duplication for some test lifecycle stuff like applying the CAPI yamls etc. We should really refactor all these out to common place.

Hard to debug on CI

Currently, when a smoke fails on CI, it's pretty impossible to say what went sideways. Yes, we do collect k0smotron controller logs but often times that does not really tell much. What we would need is also some state of thing, like a full dump of all the related objects. And possibly logs of other controllers. What I think in the end we'd need is basically a support dump like we do on k0s side for the smokes.

Move some of the standaloone k0smotron tests away from k0s bootloose suite

We don't really need that functionality, we should be able to run all the tests in similar way on top of kind.

@apedriza apedriza self-assigned this Oct 29, 2024
Copy link

The issue is marked as stale since no activity has been recorded in 30 days

@github-actions github-actions bot added the Stale label Jan 29, 2025
@apedriza apedriza added keep Exempts issues and pull requests from stale workflow and removed Stale labels Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keep Exempts issues and pull requests from stale workflow
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants