You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: