Bug 1804869
| Summary: | Pods in pending status display no conditions, unable to know that pod can't be scheduled | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Clayton Coleman <ccoleman> | |
| Component: | Management Console | Assignee: | Robb Hamilton <rhamilto> | |
| Status: | CLOSED ERRATA | QA Contact: | Yanping Zhang <yanpzhan> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.4 | CC: | aos-bugs, jokerman, rhamilto, sgoodwin, yapei | |
| Target Milestone: | --- | |||
| Target Release: | 4.5.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: The pods details page did not include conditions.
Consequence: Without the conditions, it is hard to know the status of the pod.
Fix: Add the conditions section to the pod details page.
Result: It is easier to discern the status of the pod now that conditions are included.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1807107 (view as bug list) | Environment: |
Version: 4.5.0-0.ci-2020-02-19-141327
Cluster ID: 0a55030e-bf1e-49f9-9f5d-7d797779c093
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36
|
|
| Last Closed: | 2020-07-13 17:16:20 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: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1807107 | |||
> The condition, reason, and message are all important for users to know, but the Pod details and Container details pages show nothing for the conditions. Adding the Conditions section to the bottom of the pod details page is trivial. I assume we want this for all pods regardless of status? > The conditions should be shown, and the "pending" at the top of the page This is similar to the request to have the timestamp by the status in the header. I'm unable to locate where this request was made. I know sgoodwin was looking in to it... > and in the pod status should indicate that the pod isn't schedulable. This is a not-uncommon scenario and the current UI flow makes it extremely hard to know what to do (I had to look at pod YAML) For CSVs we display "Status Reason" (with status.condition.message as a value) underneath "Status" in the CSV Details section. Do we want to do something similar here? (In reply to Robb Hamilton from comment #1) > > The conditions should be shown, and the "pending" at the top of the page > > This is similar to the request to have the timestamp by the status in the > header. I'm unable to locate where this request was made. I know sgoodwin > was looking in to it... > Original bug https://bugzilla.redhat.com/show_bug.cgi?id=1792489 was closed and Ben opened an RFE in jira https://issues.redhat.com/browse/RFE-563 Additional enhancements will be part of https://issues.redhat.com/browse/RFE-563 Checked on OCP 4.5 with payload 4.5.0-0.ci-2020-02-28-043432. Create pod that could not be scheduled successfully, check the conditions info on pod detail page, it shows Reason: "Unschedulable" and Message: "error while running "VolumeBinding" filter plugin for pod "example-0": pod has unbound immediate PersistentVolumeClaims". The bug is fixed, so move it to Verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409 |
A pod that can't be scheduled is in phase Pending with conditions: phase: Pending conditions: - type: PodScheduled status: 'False' lastProbeTime: null lastTransitionTime: '2020-02-19T18:46:05Z' reason: Unschedulable message: >- 0/6 nodes are available: 1 Insufficient cpu, 5 node(s) didn't match node selector. The condition, reason, and message are all important for users to know, but the Pod details and Container details pages show nothing for the conditions. The conditions should be shown, and the "pending" at the top of the page and in the pod status should indicate that the pod isn't schedulable. This is a not-uncommon scenario and the current UI flow makes it extremely hard to know what to do (I had to look at pod YAML)