-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HDDS-2045. Partially started compose cluster left running #1358
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
Conversation
|
/label ozone |
| && wait_for_datanodes "$COMPOSE_FILE" "${datanode_count}" \ | ||
| && sleep 10 | ||
|
|
||
| if [[ $? -gt 0 ]]; then |
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.
shellcheck:9: note: Check exit code directly with e.g. 'if mycmd;', not indirectly with $?. [SC2181]
|
💔 -1 overall
This message was automatically generated. |
elek
left a comment
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.
+1 thanks the contribution @adoroszlai
Will commit it soon.
|
Thanks @elek for committing it. |
What changes were proposed in this pull request?
If any container in the sample cluster fails to start, all successfully started containers are left running. This prevents any further acceptance tests from normal completion. This is only a minor inconvenience, since acceptance test as a whole fails either way.
This change makes sure the cluster is stopped if startup fails.
https://issues.apache.org/jira/browse/HDDS-2045
How was this patch tested?
Temporarily added fake failures in
start_docker_envandwait_for_datanodes, and verified that the cluster is stopped:Verified that the test succeeds without the fake failure.