Bug 1465157

Summary:	Launching a persistent application with a forbidden amount of storage causes poor usability
Product:	OpenShift Online	Reporter:	Will Gordon <wgordon>
Component:	Unknown	Assignee:	Abhishek Gupta <abhgupta>
Status:	NEW ---	QA Contact:	Wenjing Zheng <wzheng>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.x	CC:	chatgptlogin11, curley_65
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:

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.

Comment 6 Sarah Taylor 2024-04-19 12:40:36 UTC

It sounds like you're encountering an issue with deploying persistent applications like MySQL in OpenShift, where specifying a volume capacity below the minimum storage value leads to the application deploying without the necessary Persistent Volume (PV). This can indeed disrupt the developer workflow.

To address this, it's crucial to have warnings or validations in place prior to application deployment, notifying users about any potential issues like insufficient volume capacity. This proactive approach allows users to rectify the problem before proceeding with deployment, ensuring a smoother workflow.

For more efficient troubleshooting, you might want to consider upgrading to the latest version of OpenShift, ensuring that you have access to the most recent features and improvements. Contact on <a href="https://gbwhatsapppro-in.com/">WhatsApp GB</a> for details

Comment 7 Sarah Taylor 2024-04-23 06:02:42 UTC

Launching the Chat <a href="https://threadslogins.com/chat-gpt-login/">Chat GPT Login</a> with a forbidden amount of storage can significantly impact usability. It could lead to sluggish performance, frequent crashes, or even render the app unusable. Ensuring sufficient storage capacity is crucial for maintaining a smooth user experience and preventing frustration.