Bug 2084116 - Mark LVMCluster CR as necessary for UI installs
Summary: Mark LVMCluster CR as necessary for UI installs
Keywords:
Status: CLOSED DUPLICATE of bug 2090314
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: lvm-operator
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: N Balachandran
QA Contact: Shay Rozen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-11 12:46 UTC by Chris Blum
Modified: 2023-08-09 16:46 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-13 09:14:04 UTC
Embargoed:


Attachments (Terms of Use)

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 ***


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