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

Test wait for update #826

Merged
merged 3 commits into from
Feb 4, 2020
Merged

Test wait for update #826

merged 3 commits into from
Feb 4, 2020

Conversation

mogren
Copy link
Contributor

@mogren mogren commented Jan 31, 2020

Issue #, if available:

Description of changes:

  • Run integration tests before and after updating the CNI
  • Run e2e tests from CircleCI (part of Automate conformance testing #686)
  • Merge config files from release-1.6 branch

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@mogren mogren added the testing label Jan 31, 2020
@mogren mogren requested a review from jaypipes January 31, 2020 23:20
@mogren mogren force-pushed the test-wait-for-update branch 4 times, most recently from 14a166c to 957fe61 Compare February 1, 2020 05:54
@@ -1,15 +1,19 @@
#!/usr/bin/env bash

function down-test-cluster() {
if [[ -n "${CIRCLE_JOB:-}" ]]; then
Copy link
Contributor

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?

Copy link
Contributor Author

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
Copy link
Contributor

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?

Copy link
Contributor Author

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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ack, makes sense. ++

scripts/run-integration-tests.sh Outdated Show resolved Hide resolved

echo "Sleping for 110s"
echo "TODO: Poll and wait for updates to complete instead!"
sleep 110
Copy link
Contributor

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? :)

Copy link
Contributor Author

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.

$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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ack, makes sense. ++

@jaypipes jaypipes merged commit 73d0314 into aws:master Feb 4, 2020
@mogren mogren deleted the test-wait-for-update branch August 24, 2020 03:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants