Bug 2084116

Summary:	Mark LVMCluster CR as necessary for UI installs
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Chris Blum <cblum>
Component:	lvm-operator	Assignee:	N Balachandran <nibalach>
Status:	CLOSED DUPLICATE	QA Contact:	Shay Rozen <srozen>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.11	CC:	jolmomar, lgangava, mmuench, muagarwa, ocs-bugs, odf-bz-bot, sapillai
Target Milestone:	---
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-06-13 09:14:04 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 Chris Blum 2022-05-11 12:46:37 UTC

Description of problem (please be detailed as possible and provide log
snippests):
We need to make it obvious that the LVMCluster CR is a mandatory CR for a working LVM Operator storage. Nithya said that this is a small change to mark this CRD as mandatory - same way we do for the StorageCluster in ODF.

Version of all relevant components (if applicable):


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

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

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

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
Yes, only UI

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

Steps to Reproduce:
1. Install LVMO via OperatorHub
2. Look at the installed Operator via the Web UI


Actual results:
There should be a message telling me to create a LVMCluster CR

Expected results:
No message appears

Additional info:

Comment 2 Santosh Pillai 2022-06-13 05:02:11 UTC

This has been fixed along with https://bugzilla.redhat.com/show_bug.cgi?id=2090314

Comment 3 N Balachandran 2022-06-13 09:14:04 UTC


*** This bug has been marked as a duplicate of bug 2090314 ***