Bug 1807230

Summary:	Pipeline Builder Error Icon Missing
Product:	OpenShift Container Platform	Reporter:	Andrew Ballantyne <aballant>
Component:	Dev Console	Assignee:	Andrew Ballantyne <aballant>
Status:	CLOSED ERRATA	QA Contact:	Ruchir Garg <rgarg>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	aos-bugs, nmukherj, sbudhwar
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1807233 (view as bug list)		Environment:
Last Closed:	2020-08-04 18:02:24 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:	1807233

Description Andrew Ballantyne 2020-02-25 20:57:11 UTC

Description of problem:
There is a problem with how the errors are reported in the Pipeline Builder. An over-aggressive hook was clearing the errors as they were logged. This prevented the tasks from properly reporting when they were missing resources or parameter values.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Open the Pipeline Builder (Create Pipeline button on the Pipelines list page)
2. Add a task that contains errors (say s2i-nodejs)
3. Notice it does not report an error
4. Click on it and see that it is erroring on the lack of resources

Actual results:
An incomplete task not reporting that it is incomplete

Expected results:
A red circle + "!" icon that indicates it is incomplete

Additional info:

Comment 4 errata-xmlrpc 2020-08-04 18:02:24 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.5 image release 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