| Summary: | OSE 3.2.1.15 Scheduler fails to find fitting node due to "PodFitsPorts" event - even the necessary hostports are not bound | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Miheer Salunke <misalunk> |
| Component: | Node | Assignee: | Avesh Agarwal <avagarwa> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | DeShuai Ma <dma> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.2.1 | CC: | agoldste, aos-bugs, eparis, jokerman, mmccomas, stwalter, wmeng |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-26 23:43:24 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 4
Andy Goldstein
2016-11-10 19:57:52 UTC
Saw similar issue. Customer's router pod would not schedule to node due to PodFitsPorts but nothing was listening on that port when checking with: $ netstat -tulpn Only one other pod was running on the node, but it was a registry pod and not listening on ports 80, 443, or 1936. Restarting the master services allowed the pod to schedule again. |