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

e2e test 'restart-counted' is flaky #954

Open
sharnoff opened this issue Jun 4, 2024 · 0 comments
Open

e2e test 'restart-counted' is flaky #954

sharnoff opened this issue Jun 4, 2024 · 0 comments
Labels
a/ci Area: related to continuous integration c/autoscaling/neonvm Component: autoscaling: NeonVM

Comments

@sharnoff
Copy link
Member

sharnoff commented Jun 4, 2024

Hit this a few times over the past few weeks. Finally got around to opening an issue for it after hitting it again. A couple examples:

Seems like in general the issue is that the VM has Phase=Running and RestartCount=0 after the pod has been killed.

At first I thought it might be a race between when the controller updates the VM after restarting and when kuttl checks... but it seems like the issue is actually that it's still that way 30 seconds later?

@sharnoff sharnoff added c/autoscaling/neonvm Component: autoscaling: NeonVM a/ci Area: related to continuous integration labels Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a/ci Area: related to continuous integration c/autoscaling/neonvm Component: autoscaling: NeonVM
Projects
None yet
Development

No branches or pull requests

1 participant