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

drain-interval does not wait between drain failures #185

Open
omgrr opened this issue Jan 10, 2024 · 0 comments
Open

drain-interval does not wait between drain failures #185

omgrr opened this issue Jan 10, 2024 · 0 comments

Comments

@omgrr
Copy link

omgrr commented Jan 10, 2024

Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT

What happened:
The retry-interval does not work. I believe it got removed accidentally but it appears not to be used anywhere.
https://github.com/keikoproj/lifecycle-manager/blob/master/pkg/service/nodes.go#L72

When testing with a blocking PDB (just setting maxUnavailable: 0) to simulate a drain timeout, I would expect the total time to equal drain_timeout * drain_retries * drain-interval. However it becomes really obvious with a high drain-interval that its not being used.

What you expected to happen:

I would have expected the total time to drain a node before abandoning, to be drain_timeout * drain_retries * drain-interval.

How to reproduce it (as minimally and precisely as possible):

The easiest way is probably just to alter this test, set to the retry interval to something very large, and run make test. Since it should fail, it should sleep for the drain interval but it doesn't. And actually even the way the test is written the whole suite should fail because the Makefile is running the tests with -timeout 30s.

Alternatively you can make a blocking PDB with maxUnavailable: 0, and set the drain-interval to something very large, the retries large, and the drain timeout small.

Anything else we need to know?:

  • Kubernetes version: 1.23.17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant