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

Improve liveness probe for antrea-ovs container #861

Merged
merged 1 commit into from
Jun 29, 2020

Conversation

tnqn
Copy link
Member

@tnqn tnqn commented Jun 23, 2020

  • Increase failureThreshold to 5 and timeout to 10 seconds to avoid
    frequent restarts when the node is overloaded.

  • Set timeoutSeconds explicitly otherwise it's defaulted to 1 second,
    though it's not honored by docker CRI.

  • Keep the output of probe script so that it will be appended to the
    message of liveness failure event and be helpful to see the actual
    problem.

For #833

@antrea-bot
Copy link
Collaborator

Thanks for your PR.
Unit tests and code linters are run automatically every time the PR is updated.
E2e, conformance and network policy tests can only be triggered by a member of the vmware-tanzu organization. Regular contributors to the project should join the org.

The following commands are available:

  • /test-e2e: to trigger e2e tests.
  • /skip-e2e: to skip e2e tests.
  • /test-conformance: to trigger conformance tests.
  • /skip-conformance: to skip conformance tests.
  • /test-whole-conformance: to trigger all conformance tests on linux.
  • /skip-whole-conformance: to skip all conformance tests on linux.
  • /test-networkpolicy: to trigger networkpolicy tests.
  • /skip-networkpolicy: to skip networkpolicy tests.
  • /test-windows-conformance: to trigger windows conformance tests.
  • /skip-windows-conformance: to skip windows conformance tests.
  • /test-all: to trigger all tests (except whole conformance).
  • /skip-all: to skip all tests (except whole conformance).

These commands can only be run by members of the vmware-tanzu organization.

* Increase failureThreshold to 5 and timeout to 10 seconds to avoid
  frequent restarts when the node is overloaded.

* Set timeoutSeconds explicitly otherwise it's defaulted to 1 second,
  though it's not honored by docker CRI.

* Keep the output of probe script so that it will be appended to the
  message of liveness failure event and be helpful to see the actual
  problem.
Copy link
Contributor

@antoninbas antoninbas left a comment

Choose a reason for hiding this comment

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

LGTM

@tnqn
Copy link
Member Author

tnqn commented Jun 24, 2020

@antoninbas thanks for the quick review.

/test-all

@tnqn
Copy link
Member Author

tnqn commented Jun 29, 2020

/test-conformance
/test-networkpolicy
/test-windows-conformance

@tnqn tnqn merged commit 3311637 into antrea-io:master Jun 29, 2020
@tnqn tnqn deleted the ovs-timeout branch June 29, 2020 08:13
GraysonWu pushed a commit to GraysonWu/antrea that referenced this pull request Sep 22, 2020
* Increase failureThreshold to 5 and timeout to 10 seconds to avoid
  frequent restarts when the node is overloaded.

* Set timeoutSeconds explicitly otherwise it's defaulted to 1 second,
  though it's not honored by docker CRI.

* Keep the output of probe script so that it will be appended to the
  message of liveness failure event and be helpful to see the actual
  problem.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants