Bug 1909790

Summary: PipelineBuilder yaml view cannot be used for editing a pipeline
Product: OpenShift Container Platform Reporter: Debsmita Santra <dsantra>
Component: Dev ConsoleAssignee: Debsmita Santra <dsantra>
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.7CC: aballant, aos-bugs, nmukherj, spathak
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:47:19 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:
Description Flags
PipelineBuilder yaml view can be used for editing a pipeline none

Description Debsmita Santra 2020-12-21 16:19:36 UTC
Description of problem:
Pipeline cannot be edited using PipelineBuilder yaml view as on saving the yaml an error is thrown saying `Error "Invalid value: 0x0: must be specified for an update" for field "metadata.resourceVersion".`

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

How reproducible:

Steps to Reproduce:
1. Create a pipeline
2. Go to pipelines page
3. Click on edit pipeline kebab menu action
4. Go to yaml view
5. Edit the pipeline

Actual results:
Error alert with message `Error "Invalid value: 0x0: must be specified for an update" for field "metadata.resourceVersion".`

Expected results:
There should be no error and PipelineBuilder yaml view should work as expected.

Additional info:

Comment 2 spathak@redhat.com 2021-01-15 06:24:46 UTC
Created attachment 1747681 [details]
PipelineBuilder yaml view can be used for editing a pipeline

Comment 3 spathak@redhat.com 2021-01-15 06:48:43 UTC
Verified on build version: 4.7.0-0.nightly-2021-01-13-124141
Browser version: Chrome 84

Comment 6 errata-xmlrpc 2021-02-24 15:47:19 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.