Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upPod stuck on pending status due to hung docker daemon #4398
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Open an upstream issue please |
sspeiche
referenced this issue
Aug 28, 2015
Closed
Pod stuck on pending status due to hung docker daemon #13305
danmcp
added
priority/P2
component/kubernetes
labels
Sep 10, 2015
danmcp
assigned
ncdc
Sep 10, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
ncdc
Jun 4, 2016
Contributor
Let's plan to close this once we rebase in Kube 1.3.x, as the upstream issue has been closed for 1.3.
|
Let's plan to close this once we rebase in Kube 1.3.x, as the upstream issue has been closed for 1.3. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
@mfojtik this should be closed with yours or the next rebase, just fyi. |
openshift-bot
closed this
in
#8856
Jun 15, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
sspeiche commentedAug 27, 2015
Origin/kubernetes should detect that case when a node is not able to service request such as a hung docker daemon, terminate the execution after some period of time and log an event/message. It would also be good if it attempted to launch the pod on a different healthy node.
I hit this issue recently with an instance that had been running for about a month. Things were working fine for a couple weeks.
/version reveals:
"gitVersion": "v0.17.1-804-g496be63",
"gitCommit": "496be63",