-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
respect ExecProbeTimeout=false for dockershim #100200
respect ExecProbeTimeout=false for dockershim #100200
Conversation
Hi @jackfrancis. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
cc @andrewsykim @chewong @lachie83 It wasn't obvious to me how me might inject a feature gate config into the mocks used by Additionally, do you think it would make sense to include something like this in this PR?: |
/assign @ehashman @andrewsykim |
/ok-to-test |
/retest |
/test pull-kubernetes-e2e-aks-engine-azure |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dchen1107, ehashman, hasheddan, jackfrancis The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
flake #100556 |
/retest |
3 similar comments
/retest |
/retest |
/retest |
/retest Review the full test history for this PR. Silence the bot with an |
6 similar comments
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
@jackfrancis: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/retest Review the full test history for this PR. Silence the bot with an |
What type of PR is this?
/kind bug
What this PR does / why we need it:
This PR ensures that the kubelet ExecProbeTimeout feature gate is respected when evaluating whether to timeout an exec probe's context when its configured
timeoutSeconds
period has expired.The current implementation has the effect of ignoring the probe outcome after the
timeoutSeconds
period has expired.Which issue(s) this PR fixes:
Fixes #100198
Special notes for your reviewer:
I've tested that a build with this PR restored the expected behavior, where timeouts are simply ignored.
The original PR that fixed the buggy timeout behavior does not reproduce this new "probes always succeed pathology" according to my tests:
#94115
Further testing confirmed that this commit is the first that reproduces this new bug:
#96495
It appears that this surface area change ommitted the ExecProbeTimeout feature gate:
https://github.com/kubernetes/kubernetes/pull/96495/files#diff-de4678da3e9d01e8ee0aadd641deb2ffec3a53c8603476509e59fa8dc5449deaL117
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: