-
Notifications
You must be signed in to change notification settings - Fork 230
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 1462067 - Don't set propagationPolicy when deleting pod immediately #1792
Conversation
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.
Change LGTM
We've been trying to avoid making any special exceptions in the console though, so far every weird case we have hit has been a bug with GC. |
If you're trying to force delete something, foreground propagation seems wrong. But this comment worries me:
|
Agreed this change is OK then and we need to spawn a separate issue for the fact that GC + Terminating can get pods permanently stuck in storage. |
[merge] |
looks like the webdriver start flake [merge] |
Flake
[merge] |
Flake #1684 |
Evaluated for origin web console merge up to 636745e |
Origin Web Console Merge Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_web_console/1618/) (Base Commit: 1c22134) (PR Branch Commit: 636745e) |
This change removes the propagation policy from delete options when force deleting a pod from the web console. It makes the web console DELETE request consistent with
oc delete --now --force
(only when delete immediately is checked).@jwforres WIP because I haven't been able to verify against a pod that is really stuck in terminating. I'm concerned we might have a GC bug with propagation policy foreground and grace period 0.
@derekwaynecarr Do you know how I can purposely get a pod stuck in Terminating state to test this fix?
cc @deads2k
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1462067