HDDS-5494. Reduce retry in Kubernetes test #2461
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
kubernetes tests wait for cluster startup, checking some conditions with retry. In worst case all conditions are checked 100 times with 3 seconds delay, so the test may take 15 minutes to fail.
Skip waiting for SCM and OM readiness if retries for previous conditions are exhausted.
https://issues.apache.org/jira/browse/HDDS-5494
How was this patch tested?
Currently the test in
ozone
env. fails to start the cluster, so the change is verified by the failing CI check:https://github.com/adoroszlai/hadoop-ozone/runs/3159798487#step:6:797
The happy path is verified by successful startup in
getting-started
env.:https://github.com/adoroszlai/hadoop-ozone/runs/3159798487#step:6:172