-
Notifications
You must be signed in to change notification settings - Fork 23
Bug 1758343: pkg/drain: always honor pod termination timeout #130
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
Bug 1758343: pkg/drain: always honor pod termination timeout #130
Conversation
0248315 to
f7081a8
Compare
|
@runcom: This pull request references Bugzilla bug 1758343, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
|
@enxebre @michaelgugino ptal |
f7081a8 to
3afe7e1
Compare
michaelgugino
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.
This looks good to me. Let's add a BZ link for tracking.
it's linked in the title here and #130 (comment) - do you want it in the commit message as well? |
michaelgugino
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.
/lgtm
3afe7e1 to
412f4a9
Compare
|
Document the pod/library interaction on the option type? (if we keep the option; I'm fine dropping it). |
I'll hold that on #130 (comment) |
… timeout Honoring the drain's library termination timeout can cause unnecessary timeout on delete. The MCO is wronly setting a 600s termination timeout for every pod which is wrong. Fix MCO and any other user who might have set an hard timeout exceeding the pod's termination timeout. Signed-off-by: Antonio Murdaca <runcom@linux.com>
412f4a9 to
b891cff
Compare
ok, fixed, I believe it's good to go now since there's quite a bit of a rush to get this in and get the 4.2 blocker fixed in MCO |
|
/retest |
|
@runcom: once the present PR merges, I will cherry-pick it on top of release-4.2 in a new PR and assign it to you. In response to this:
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. |
|
/approve We are in the process of migrating to release-4.X branches. Meanwhile, for porting |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enxebre 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 |
|
/cherrypick openshift-4.2-cluster-api-0.1.0 |
|
@runcom: once the present PR merges, I will cherry-pick it on top of openshift-4.2-cluster-api-0.1.0 in a new PR and assign it to you. In response to this:
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. |
|
/lgtm |
|
/cherrypick openshift-4.1-cluster-api-0.0.0-alpha.4 |
|
@runcom: once the present PR merges, I will cherry-pick it on top of openshift-4.1-cluster-api-0.0.0-alpha.4 in a new PR and assign it to you. In response to this:
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. |
|
@runcom: All pull requests linked via external trackers have merged. Bugzilla bug 1758343 has been moved to the MODIFIED state. In response to this:
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. |
|
@runcom: new pull request created: #131 In response to this:
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. |
|
@runcom: new pull request created: #132 In response to this:
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. |
|
Just to make sure, the local consumer has always set the timeout -1, so all good there. |
Honoring the drain's library termination timeout can cause unnecessary
timeout on delete.
The MCO is wronly setting a 600s termination timeout for every pod which
is wrong.
Fix MCO and any other user who might have set an hard timeout exceeding
the pod's termination timeout.
Signed-off-by: Antonio Murdaca runcom@linux.com