Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1834822

Summary: Cannot edit deployment triggers
Product: OpenShift Container Platform Reporter: divgupta
Component: Dev ConsoleAssignee: divgupta
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: high    
Version: 4.4CC: aos-bugs, nmukherj, spathak
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1839019 (view as bug list) Environment:
Last Closed: 2020-07-13 17:37:59 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: 1839019    
Attachments:
Description Flags
During creation
none
While edit none

Description divgupta 2020-05-12 13:41:58 UTC 
Description of problem:
Not able to edit deployment triggers.

How reproducible: Always

Steps to Reproduce:
1. import an app from git as a deployment.
2. by default both "Auto deploy when new image is available" and "Auto deploy     when deployment configuration changes" options are checked.
3. complete the import.
4. edit the newly created workload.
5. in the form observe that both options re unchecked.

Actual results:
Deployment triggers cannot be edited.

Expected results:
Deployment triggers should be edited.
Comment 3 spathak@redhat.com 2020-05-21 23:01:07 UTC 
Created attachment 1690902 [details]
During creation
Comment 4 spathak@redhat.com 2020-05-21 23:01:46 UTC 
Created attachment 1690903 [details]
While edit
Comment 5 spathak@redhat.com 2020-05-21 23:02:33 UTC 
Verified on build version: 4.5.0-0.ci-2020-05-21-034945
Browser version: Firefox 73
Comment 6 errata-xmlrpc 2020-07-13 17:37:59 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:2409