Red Hat Bugzilla – Bug 1465157
Launching a persistent application with a forbidden amount of storage causes poor usability
Last modified: 2017-08-17 02:58:27 EDT
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: v184.108.40.206 (online version 220.127.116.11)
Kubernetes Master: v1.5.2+43a9be4
Steps to Reproduce:
1. Add MySQL Persistent to a project
2. Specify a Volume Capacity of 256Mi
3. Click create
Application is created, and a warning is shown after the fact
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.
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.