Bug 1839115

Summary: Environment Variables can not be added to knative service through Add flow
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: Dev ConsoleAssignee: Jaivardhan Kumar <jakumar>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: high    
Version: 4.4CC: aos-bugs, cvogt, nmukherj
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Unable to add environment variables for knative service Consequence: for the apps where envVariables would be need might not work as expected Fix: Added support for Environment variables in advance section Result: User can add environment variables for knative Service
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-23 00:57:26 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: 1839114    
Bug Blocks:    

Description OpenShift BugZilla Robot 2020-05-22 14:10:00 UTC
+++ This bug was initially created as a clone of Bug #1839114 +++

Description of problem:
Environment Variables can not be added to knative service through Add flow

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


How reproducible: always


Steps to Reproduce:
1. Install Serverless operator
2. go to devConsole -> add -> git import
3. select knative service

Actual results: Can't add environment variables for knative 


Expected results: Should be able to add environment variables for knative 


Additional info:

Comment 3 Gajanan More 2020-06-15 10:48:59 UTC
I have verified it on:
Build: 4.4.0-0.ci-2020-06-15-004655
Browser: Google Chrome Version 81.0.4044.129
Marking this as verified.

Comment 5 errata-xmlrpc 2020-06-23 00:57:26 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:2580