Bug 1394044

Summary: Validation of environment variable names is overly strict when editing DC
Product: OKD Reporter: Justin Pierce <jupierce>
Component: Management ConsoleAssignee: Jessica Forrester <jforrest>
Status: CLOSED CURRENTRELEASE QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.xCC: aos-bugs, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-09 21:50:42 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 Justin Pierce 2016-11-10 21:39:48 UTC 
Description of problem:
When editing environment variables in the DC->Edit page, environment variables starting with underscores fail validation.
Some environment variables do start with _ . This validation does not appear to take place on the "Environment" tab of the DC which permits environment variables which start with _.

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

How reproducible:
100%

Steps to Reproduce:
1. Create a deployment config
2. On the environment tab, add an environment variable _TEST=1
3. Save your changes
4. Select "Edit" from the DC Actions drop down box

Actual results:
I see a validation error on _TEST

Expected results:
_TEST is a valid environment variable. 


Additional info:
Comment 1 Yadan Pei 2016-11-14 06:33:02 UTC 
Checked against v1.4.0-alpha.1+9c4f9ee-179

Now user could succeed in adding environment variable _TEST=1 on DC Environment Tab & Edit DC page

Move to VERIFIED