Bug 1767961

Summary:	Pipeline doesn't start because of trigger type
Product:	OpenShift Container Platform	Reporter:	Andrew Ballantyne <aballant>
Component:	Dev Console	Assignee:	cvogt
Status:	CLOSED ERRATA	QA Contact:	Ruchir Garg <rgarg>
Severity:	unspecified	Docs Contact:
Priority:	urgent
Version:	4.2.0	CC:	aos-bugs, cvogt, decarr, jakumar, nmukherj, rgarg, spathak, ssadeghi
Target Milestone:	---
Target Release:	4.2.z
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1763725	Environment:
Last Closed:	2019-11-19 13:49:01 UTC	Type:	---
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:	1763725
Bug Blocks:

Description Andrew Ballantyne 2019-11-01 18:13:07 UTC

+++ This bug was initially created as a clone of Bug #1763725 +++

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-13 09:05:38 UTC

Verified

Comment 4 errata-xmlrpc 2019-11-19 13:49:01 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-2019:3869

Comment 5 Red Hat Bugzilla 2023-09-14 05:45:23 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days