Bug 1312819

Summary:	Can not add Environment Variables on buildconfig edit page
Product:	OpenShift Container Platform	Reporter:	Yadan Pei <yapei>
Component:	Management Console	Assignee:	Jakub Hadvig <jhadvig>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.2.0	CC:	aos-bugs, jokerman, mmccomas, tdawson
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-12 16:30:36 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 Yadan Pei 2016-02-29 10:28:32 UTC

Description of problem:
On buildconfig edit page, When click "Add" to Environment Variables, env vars couldn't be added

Version-Release number of selected component (if applicable):
oc v3.1.1.907-1-g0755947
kubernetes v1.2.0-alpha.7-703-gbc4550d

How reproducible:
Always

Steps to Reproduce:
1. Create application via web console
2. Browse -> Builds -> <bc_name> -> Edit -> Environment Variables -> Input Name/Value -> Add

Actual results:
2. Click on "Add" button for Environment Variables didn't get response, env vars are not added

Expected results:
2. Environment Variables should be added successfully

Additional info:

Comment 1 Jakub Hadvig 2016-02-29 21:50:38 UTC

Fixed in : https://github.com/openshift/origin/pull/7691

Comment 2 Yadan Pei 2016-03-01 07:29:33 UTC

will check when devenv-rhel7_3570 is ready

Comment 3 Yadan Pei 2016-03-02 01:40:23 UTC

will check when new OSE puddle is ready

Comment 4 Yadan Pei 2016-03-03 02:28:44 UTC

checked on 2016-03-02.2 puddle, issue is fixed, could add env vars successfully now

move to VERIFIED

Comment 6 errata-xmlrpc 2016-05-12 16:30:36 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/RHSA-2016:1064