Bug 1778958

Summary: Support Pipeline Operator 0.9.0
Product: OpenShift Container Platform Reporter: Andrew Ballantyne <aballant>
Component: Dev ConsoleAssignee: Andrew Ballantyne <aballant>
Status: CLOSED ERRATA QA Contact: Ruchir Garg <rgarg>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, nmukherj, spathak
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: v0.9.x+ of the OpenShift Pipeline Operator would not work with the UI code after removal of an API reference (serviceAccount was replaced with serviceAccountName). Consequence: The Pipelines created in OpenShift could possibly not create Pipeline Runs if they used the aforementioned key. Fix: Don't explicitly use the key and migrate if found. Result: Pipelines will again work with v0.9.x+ of the OpenShift Pipeline Operator.
 Story Points: ---
Clone Of:
: 1788201 (view as bug list) Environment:
Last Closed: 2020-05-13 21:53:31 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: 1788201, 1789119    
Attachments:
Description Flags
Support Pipeline Operator 0.9.0 none

Description Andrew Ballantyne 2019-12-02 22:52:18 UTC 
Description of problem:
0.8.0 of the Pipeline Operator has deprecated the usage of 'spec.serviceAccount' in PipelineRuns. In 0.9.0 it will become an error to pass 'serviceAccount'.

The new field 'serviceAccountName' is to replace it.


Version-Release number of selected component (if applicable):
Pipeline Operator 0.9.0, 0.8.0
OpenShift 4.4, 4.3, 4.2

How reproducible:
Only when serviceAccounts are being used.


Steps to Reproduce:
1. Create a Pipeline
2. Manually CLI upload a Pipeline Run with a 'spec.serviceAccount' property equal to something
3. Upgrade to Pipeline Operator 0.9.0
4. From the UI, re-run the Pipeline Run that was uploaded

Actual results:
Tekton error saying `serviceAccount` is an invalid field

Expected results:
For this not to be a problem.

Additional info:
This will likely be hard to test as the Canary build today is 0.8.0 but it is soon to be promoted to the dev-preview (main available subscription), making room for 0.9.0 to become the Canary build.

It's not sure how long the Canary build will be 0.9.0, but once it gets promoted to dev-preview it will break the UI if this change is not there.
Comment 2 spathak@redhat.com 2020-01-08 21:11:16 UTC 
Verified on build version: 4.4.0-0.ci-2020-01-07-061008
Comment 3 spathak@redhat.com 2020-01-08 21:12:49 UTC 
Created attachment 1650842 [details]
Support Pipeline Operator 0.9.0

Pipeline worked after updating to 0.9x
Comment 5 errata-xmlrpc 2020-05-13 21:53:31 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:0581