-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Pod status.phase shall not transition from Succeeded to Pending #17011
Comments
P0 after the associated issue #16870 |
Uh oh |
fyi @derekwaynecarr might be related to our old friend https://bugzilla.redhat.com/show_bug.cgi?id=1486356 |
I was unable to reproduce this on kubernetes release-1.7 branch or v1.7.6. Here are the logs where things go sideways:
PLEG picks up on the container moving from running -> exited and the pod is marked as However, then we failed to get the container status because it doesn't exist anymore, and the pod is seen as orphaned. PLEG goes from exited -> non-existent and a new status is created for the pod starting an |
This is caused by #16913 backported from kube 1.8. This is reproducible in kube release-1.8 upstream. |
Opened upstream issue kubernetes/kubernetes#54499. We'll see if they want to revert or fix. Hopefully we'll get a quick response. |
Automatic merge from submit-queue. UPSTREAM: 54593: Removed containers are not always waiting xref kubernetes/kubernetes#54593 fixes #17011
for reference this still seems broken #17595 just now it is Failed -> Succeeded |
Pod status.phase shall not transition from
Succeeded
toPending
.(Note that this is dependent on timing of the deletion.)
I think this is the reason we are seeing multiple deployer pods running for DeploymentConfigs.
Version
Steps To Reproduce
Current Result
Pod transitions from
Succeeded
toPending
after being deleted.Expected Result
Once Pod reaches phase
Succeeded
it stays there.Additional Information
$ cat ~/tmp/pod/pod.yaml
$ oc observe pods --output=gotemplate -a '{{.}}'
The text was updated successfully, but these errors were encountered: