+++ This bug was initially created as a clone of Bug #1807230 +++ 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:
Bulk assigning all to Gajanan for verification.
@aballant The equivalent jira(ODC-3118) is in the In Review state, should I change the status of this bugzilla?
I moved ODC-3118 to QE Review, it was merged and just got left behind.
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, 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:0581