Bug 2050271
| Summary: | Latest pipeline run should be listed on the top of the pipeline run list | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Karthik Jeeyar <kjeeyar> | ||||
| Component: | Dev Console | Assignee: | Debsmita Santra <dsantra> | ||||
| Status: | CLOSED ERRATA | QA Contact: | spathak <spathak> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4.9 | CC: | aos-bugs, dsantra, nmukherj, ppitonak | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.9.z | ||||||
| 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: | 2022-02-28 20:50:16 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: | 2054244 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
Verified on build version: 4.9.0-0.nightly-2022-02-23-182709 Browser: Google Chrome 98 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 (Low: OpenShift Container Platform 4.9.23 bug fix and security update), 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/RHSA-2022:0655 |
Created attachment 1858916 [details] Pipeline run sort order Description of problem: Pipeline run list shows the recently created pipeline run in the middle of the list. Version-Release number of selected component (if applicable): 4.9 How reproducible: Always Steps to Reproduce: 1. Create few pipeline runs in a namespace 2. Trigger a rerun from an existing pipeline run in the list Actual results: Newly created pipeline run is listed in between the existing pipeline runs. Expected results: Newly created pipeline run should be always on the top of the list Additional info: Couldn't reproduce this issue in 4.10 clusters.