Bug 1916378 - Pipeline Runs with skipped Tasks incorrectly show Tasks as "Failed"
Summary: Pipeline Runs with skipped Tasks incorrectly show Tasks as "Failed"
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.5
Hardware: x86_64
OS: Linux
Target Milestone: ---
: 4.6.z
Assignee: Andrew Ballantyne
QA Contact: spathak@redhat.com
Harsh Mishra
Depends On: 1880389
TreeView+ depends on / blocked
Reported: 2021-01-14 16:37 UTC by Andrew Ballantyne
Modified: 2021-04-22 10:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, when conditional tasks failed, the completed pipeline runs showed a permanent pending task for each failed conditional task. This issue has been fixed by disabling the failed conditional tasks and by adding skipped icons to them. This gives a better picture of the state of the pipeline run.
Clone Of: 1880389
Last Closed: 2021-02-22 13:54:32 UTC
Target Upstream Version:

Attachments (Terms of Use)
Pipeline Runs with skipped Tasks correctly show Tasks as "Failed" (52.89 KB, image/png)
2021-02-17 10:32 UTC, spathak@redhat.com
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 7843 0 None closed [release-4.6] Bug 1916378: fix skipped tasks in conditional pipelines 2021-02-16 11:42:34 UTC
Red Hat Product Errata RHBA-2021:0510 0 None None None 2021-02-22 13:54:42 UTC

Comment 3 spathak@redhat.com 2021-02-17 10:32:42 UTC
Created attachment 1757521 [details]
Pipeline Runs with skipped Tasks correctly show Tasks as "Failed"

Comment 4 spathak@redhat.com 2021-02-17 11:21:26 UTC
Verified on build version: 4.6.0-0.nightly-2021-02-13-034601
Browser version: Chrome 84

Comment 6 errata-xmlrpc 2021-02-22 13:54:32 UTC
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 (OpenShift Container Platform 4.6.18 bug fix 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.


Note You need to log in before you can comment on or make changes to this bug.