-
Notifications
You must be signed in to change notification settings - Fork 741
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
Test wait for update #826
Test wait for update #826
Conversation
14a166c
to
957fe61
Compare
957fe61
to
bd54907
Compare
@@ -1,15 +1,19 @@ | |||
#!/usr/bin/env bash | |||
|
|||
function down-test-cluster() { | |||
if [[ -n "${CIRCLE_JOB:-}" ]]; 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.
Why would you want to disable the cluster delete when running in CI?
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.
Just making it more verbose. See comment below.
$TESTER_PATH eks create cluster --path $CLUSTER_CONFIG 2>> $CLUSTER_MANAGE_LOG_PATH 1>&2 || | ||
(echo "failed. Check $CLUSTER_MANAGE_LOG_PATH." && exit 1) | ||
echo "ok." | ||
fi |
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.
I'm confused why you're changing the above depending on whether it's running in CI or not?
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.
It's just changing the logging output. By default, CircleCI will terminate any test after 10 minutes fi there is no console output. That can be changed by setting no_output_timeout
for the job, but when you have to wait 40 minutes it's more interesting to see what is going on.
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.
ack, makes sense. ++
|
||
echo "Sleping for 110s" | ||
echo "TODO: Poll and wait for updates to complete instead!" | ||
sleep 110 |
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.
why 110 seconds? is that a magic value? :)
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.
Yes, for now. The test cluster has 3 nodes, and the rolling update is using the default grace period of 30s, so it takes around 30s to shut down each node, and another 5-10 seconds to start up. It's ok to start the test once all old ipamd pods have shut down.
bd54907
to
42716c4
Compare
$TESTER_PATH eks create cluster --path $CLUSTER_CONFIG 2>> $CLUSTER_MANAGE_LOG_PATH 1>&2 || | ||
(echo "failed. Check $CLUSTER_MANAGE_LOG_PATH." && exit 1) | ||
echo "ok." | ||
fi |
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.
ack, makes sense. ++
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.