Bug 1465157 - Launching a persistent application with a forbidden amount of storage causes poor usability
Summary: Launching a persistent application with a forbidden amount of storage causes ...
Keywords:
Status: NEW
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Unknown
Version: 3.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Abhishek Gupta
QA Contact: Wenjing Zheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-26 20:03 UTC by Will Gordon
Modified: 2023-05-15 19:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Will Gordon 2017-06-26 20:03:40 UTC
Description of problem:
Launching a persistent application, like MySQL Persistent, and specifying a volume capacity below the minimum storage value, causes the application to deploy, but without the PV, which can cause a confusing developer workflow.

Version-Release number of selected component (if applicable):
OpenShift Master:  v3.5.5.28 (online version 3.5.0.20)
Kubernetes Master: v1.5.2+43a9be4

How reproducible:
Always

Steps to Reproduce:
1. Add MySQL Persistent to a project
2. Specify a Volume Capacity of 256Mi
3. Click create

Actual results:
Application is created, and a warning is shown after the fact

Expected results:
A warning should be shown before the application is allowed to be created, allowing the user to rectify the issue and continue to deploy the application as intended.

Additional info:

Comment 1 Steve Speicher 2017-07-19 01:35:25 UTC
We could easily fix this for Online Starter by just removing the parameter in the template (just setting it directly). It is slightly a hack but will fix the problem probably for over 80% of the cases.


Note You need to log in before you can comment on or make changes to this bug.