Bug 1763725 - Pipeline doesn't start because of trigger type
Summary: Pipeline doesn't start because of trigger type
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.2.0
Hardware: All
OS: All
urgent
unspecified
Target Milestone: ---
: 4.3.0
Assignee: cvogt
QA Contact: Ruchir Garg
URL:
Whiteboard:
Depends On:
Blocks: 1767961
TreeView+ depends on / blocked
 
Reported: 2019-10-21 12:43 UTC by Jaivardhan Kumar
Modified: 2020-01-23 11:08 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: When the Pipeline Operator upgraded to 0.7.x the existing code was using an invalid property that the Operator deprecated in 0.6.x. Consequence: The Pipelines could no longer be started as it gave a Pipeline Operator error. Fix: Update the code to be compatible with the new spec the Pipeline Operator is working with. Result: The user could start Pipelines from the UI again.
Clone Of:
: 1767961 (view as bug list)
Environment:
Last Closed: 2020-01-23 11:08:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 3086 0 'None' closed Bug 1763725: fix(tekton-migration): Fix trigger type and resource issue 2020-04-27 13:05:49 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:08:56 UTC

Description Jaivardhan Kumar 2019-10-21 12:43:31 UTC 
Description of problem:
After Tekton operator migrated to 0.7.0 unable to start Pipeline from UI because of Trigger Type and few other issues.

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


How reproducible:
Try starting a Pipeline from devconsole UI

Steps to Reproduce:
1. Select a namespace where Pipelines are available and click on the Pipeline Tab.
2. Try starting a Pipeline using the kebab actions
3. Either an Alert is thrown or an error is encountered and the Pipeline doesn't start or fails just after start

Actual results:
Either an Alert is thrown or an error is encountered and the Pipeline doesn't start or fails just after the start

Expected results:
Pipeline should have started successfully

Additional info:
Comment 2 spathak@redhat.com 2019-11-04 15:09:52 UTC 
The bug has been verified
Comment 3 Andrew Ballantyne 2019-11-04 15:10:47 UTC 
OpenShift PR: https://github.com/openshift/console/pull/3086
Comment 5 errata-xmlrpc 2020-01-23 11:08:26 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, 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:0062
Note You need to log in before you can comment on or make changes to this bug.