-
Notifications
You must be signed in to change notification settings - Fork 506
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
[#3810] forbid start when should be resumed #3965
Conversation
@digikata can you triage please. |
The detection looks good, but probably needs a bats test. This sequence fails to resume:
|
working on a bat test. I think it might suffer from version discrepancy between (stable) and (dev), but valuable to have nonetheless. |
Yes, the test could be saved in an "incoming" directory that is maybe only run for new versions, then it can be moved in a later PR. |
We do have a mechanism in bat tests to skip tests if running on stable, eg:
once we release a new stable we could remove that block |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! It's a nice improvement in the local cluster shutdown/resume behavior @avikam
* forbid start when should be resumed * fix resume regression * bats * bats - remove comments
* forbid start when should be resumed * fix resume regression * bats * bats - remove comments
Completing issue 3810.
This change adds a pre-flight check to the local installation mode, to verify no previous local config file exists, as an indication to a cluster that wasn't properly deleted.