| Summary: | Pod pending problem without events/reasons | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Miheer Salunke <misalunk> |
| Component: | Node | Assignee: | Solly Ross <sross> |
| Status: | CLOSED WORKSFORME | QA Contact: | DeShuai Ma <dma> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.1.0 | CC: | agoldste, aos-bugs, jkaur, jokerman, misalunk, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-02-26 16:57:54 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Comment 2
Andy Goldstein
2016-02-11 14:30: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 |