Bug 1440712

Summary: [free][free-stg][free-int]UI Message of Volumn Capacity on template Parmeter page should be 1Gi, not 512M or 2Gi.
Product: OpenShift Online Reporter: yufchang <yufchang>
Component: WebsiteAssignee: Abhishek Gupta <abhgupta>
Status: NEW --- QA Contact: yasun
Severity: low Docs Contact:
Priority: low    
Version: 3.xCC: aos-bugs
Target Milestone: ---Keywords: OnlineStarter
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: 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:
Attachments:
Description Flags
UI page none

Description yufchang 2017-04-10 10:38:06 UTC 
Created attachment 1270451 [details]
UI page

Description of problem:
When creating application from web console, on Parameter page, the message of Volum Capacity is "Volume space available for data, e.g. 512Mi, 2Gi", This message would  mislead users since PVC limitrange of Online is 1Gi.

Version-Release number of selected component (if applicable):
Openshift 3.5.5.3 
https://console.free-stg.openshift.com/

How reproducible:
Always

Steps to Reproduce:
1 . Create a new project;
2. "Add to" add application to project and then check Parameter page;
3. Modify "Volume Capacity" according to the message "Volume space available for data, e.g. 512Mi, 2Gi";
4. oc describe limitrange resource-limits;

Actual results:
3.Message is "Volume space available for data, e.g. 512Mi, 2Gi";

Expected results
Message should be correct. PVC limitrange is 1Gi, not 512Mi , or 2Gi
Comment 1 Jessica Forrester 2017-04-10 13:19:55 UTC 
This would just need to be fixed in the version of the template used in Online.
Comment 2 Abhishek Gupta 2017-04-10 17:34:57 UTC 
This change will need to be made for each template that includes a volume. At the moment, we are not maintaining separate lists of templates for free and paid tier. This will increase the maintenance overhead for minimal benefit. We need to look into automating some of these changes for Online - parameter descriptions, deployment strategy changes from "Rolling" to "Recreate", etc.

Marking it as low severity for now, till we get said automation in place.