Bug 1878700

Summary:	Could not create Pipeline Trigger with Pipeline Operator 1.1
Product:	OpenShift Container Platform	Reporter:	Christoph Jerolimov <cjerolim>
Component:	Dev Console	Assignee:	Christoph Jerolimov <cjerolim>
Status:	CLOSED ERRATA	QA Contact:	Gajanan More <gamore>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	4.6	CC:	aballant, aos-bugs, nmukherj
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 16:40:46 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:	1880376

Description Christoph Jerolimov 2020-09-14 11:25:20 UTC

Description of problem:
EventListener References to TriggerBindings was changed in OpenShift Pipeline Operator 1.1 (currently only available as preview).

In 0.5.0 (we didn't see this version in the Operator) they deprecated spec.triggers[].bindings[].name

In 0.6.0 (TP2 - 1.1 of the Operator) it has been removed in favour of deprecated spec.triggers[].bindings[].ref

Version-Release number of selected component (if applicable):
Pipeline Operator v1.1

How reproducible:
Always

Steps to Reproduce:
1. Add a Pipeline
2. Try to "Add Trigger" on it

Actual results:
An error saying `name` is not a supported field:

Expected results:
To successfully add a trigger.

Additional info:
None.

Comment 2 Andrew Ballantyne 2020-09-24 20:31:13 UTC

Verified on 4.6.0-0.nightly-2020-09-24-095222
Chrome 85.0.4183.102

Comment 5 errata-xmlrpc 2020-10-27 16:40:46 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 GA Images), 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:4196