Bug 1912558
| Summary: | TaskRun list and detail screen doesn't show Pending status | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Mohammed Saud <msaud> |
| Component: | Dev Console | Assignee: | Mohammed Saud <msaud> |
| Status: | CLOSED ERRATA | QA Contact: | Gajanan More <gamore> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.7 | CC: | aos-bugs, dsantra, nmukherj |
| Target Milestone: | --- | ||
| Target Release: | 4.7.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-02-24 15:49:41 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: | |||
this is verified on 4.7.0-0.nightly-2021-01-12-203716 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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-2020:5633 |
Description of problem: When OpenShift Pipelines started a Pipeline but there are not enough resources available to run a task it should be displayed as Pending (maybe with reason ExceededNodeResources) instead of Running. Similar to the tkn cli (tkn taskrun list). To make it clear: The pipeline status is shown correct (Running). The PipelineRun detail screen also pretend that the task is running by showing a spinner. It would be cool to show the same information here as well ?!? Prerequisites (if any, like setup, operators/versions): OpenShift Pipelines operator (tested with version 1.1.1) Steps to Reproduce Create a new namespace Add LimitRange and Pipeline from the attached yaml file Start as many PipelineRuns you need to exceed your memory limits (on my machine with a limit of 2 GB the second build waits already on the first one) Actual results: TaskRun list and detail page shows that all TaskRuns are "Running" Expected results: TaskRun list and detail page should show the same infos then the tkn cli (tkn taskrun list. The first TaskRun should show "Running" and the second "Pending". (Maybe with the reason ExceededNodeResources on the detail page??) Reproducibility (Always/Intermittent/Only Once): Always Build Details: Tested only with 4.7 master