Bug 2143378

Summary:	[RFE] Implement a warning mechanism on storage Class/PVC creation for use cases around postgres and other DB services like MySQL
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Mike Hackett <mhackett>
Component:	management-console	Assignee:	Timothy Asir <tjeyasin>
Status:	CLOSED CANTFIX	QA Contact:	Prasad Desala <tdesala>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.11	CC:	etamir, jefbrown, madam, nthomas, ocs-bugs, odf-bz-bot, skatiyar, vumrao
Target Milestone:	---	Keywords:	FutureFeature
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:	2022-12-12 07:03:34 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:
Embargoed:

Description Mike Hackett 2022-11-16 18:30:18 UTC

Description of problem (please be detailed as possible and provide log
snippests):

Implement a warning mechanism on storage Class/PVC creation for use cases around postgres and other DB services like MySQL.

We should flag users upon creation of a storage class or PVC that is intended to back a DB workload such as postgres in which utilizing RBDs as opposed to CephFS RWX PVC's would be a safer choice.

Please see documentation BZ: 

https://bugzilla.redhat.com/show_bug.cgi?id=2141891

And known issue:

https://access.redhat.com/solutions/6835851

Version of all relevant components (if applicable):
ODF 4.9, 4.10, 4.12

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

Yes, possible data corruption leading to broken files and manual recovery needed.

Is there any workaround available to the best of your knowledge?

https://access.redhat.com/solutions/6835851

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?

Multiple customers experienced issue, QE/Engineering unable to reproduce.

Can this issue reproduce from the UI?

No

If this is a regression, please provide more details to justify this:

No