Bug 1305964 - Pod pending problem without events/reasons
Summary: Pod pending problem without events/reasons
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Solly Ross
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-09 16:59 UTC by Miheer Salunke
Modified: 2019-10-10 11:09 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-26 16:57:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 2 Andy Goldstein 2016-02-11 14:30:26 UTC
Could you please post the node log file with more context? I'd like to see the following, if possible:

- Node service startup before it was restarted. This will be sometime before Feb 06 23:56:10 (beginning of attached log file)
- Node service startup after it was restarted
- Log lines around the time the pod actually started (post node service restart)

Comment 3 Miheer Salunke 2016-02-11 14:37:26 UTC
Description of problem:

Without any reason we are getting multiple pods in pending state and the state never changes. 
The only solution to solve the problem was to restart the service atomic-openshift-node on the node.
It was like something on the node was blocked but we don't know what and we consider that if it was really something blocked a timeout should be implemented to avoid unlimited "pending" state on a node (other nodes were available).


The solution was to restart the atomic-openshift-node service.

Version-Release number of selected component (if applicable):
3.1.0.4

How reproducible:
At certain times, we don't know how to reproduce this problem

Steps to Reproduce:
1. At certain times, we don't know how to reproduce this problem
2.
3.

Actual results:
The pods shall run fine

Expected results:
The pods remain in pending state


Note You need to log in before you can comment on or make changes to this bug.