-
Bug
-
Resolution: Won't Do
-
Minor
-
4.9.z
-
Quality / Stability / Reliability
-
False
-
None
-
None
-
None
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
Undefined
-
None
-
None
-
None
-
None
Description of problem:
The initial implementation of the pods side panel(ODC-1148) states that:
- it should sort the list of pods with primary of status (errors first) and secondary of update time (most recent first)
- it should list all error pods or at most 3 pods<...>
But the pods list sort function does not seem to show terminating pods as errord pods. See 0.gif
When an container image is not found, the pod is also jumping around. See unexpected-error-order.gif
Prerequisites (if any, like setup, operators/versions):
None
Steps to Reproduce
- Create a deployment with multiple pods
- Open deployment side panel for pods
- Delete one or more pods through the CLI, or in another tab
Actual results:
Terminating pods are not shown first between errors and running pods, but are shown randomly in the list. But they were updated last.
Expected results:
Terminated pods should be grouped by the pod status.
Recommended status order: Error, Pending, Running, Terminated, Evicated
For pods with the same status order them by created date and name after that.
https://github.com/openshift/console/pull/9383#issuecomment-876768945
Reproducibility (Always/Intermittent/Only Once):
Always
Additional info:
More context and additional info in this PR: https://github.com/openshift/console/pull/9383
- relates to
-
ODC-6058 Revisit rules around pod display order in topology side panel
-
- Closed
-