Bug 2054545 - Modify the LVMCluster CRD to move the deviceClasses into a section called storage
Summary: Modify the LVMCluster CRD to move the deviceClasses into a section called sto...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: lvm-operator
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ODF 4.10.0
Assignee: N Balachandran
QA Contact: Shay Rozen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-15 08:00 UTC by N Balachandran
Modified: 2023-08-09 16:46 UTC (History)
6 users (show)

Fixed In Version: 4.10.0-166
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-21 09:12:45 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage lvm-operator pull 117 0 None open Bug 2054545: [release-4.10] LVMCluster CRD changes 2022-02-22 12:39:17 UTC

Description N Balachandran 2022-02-15 08:00:27 UTC 
Description of problem (please be detailed as possible and provide log
snippests):

Change 
LVMCluster.Spec.DeviceClasses to LVMCluster.Spec.Storage.DeviceClasses.
Ditto for the status field.


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)?


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


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?


Can this issue reproduce from the UI?


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


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:
Comment 5 Shay Rozen 2022-03-02 11:45:49 UTC 
Cluster is working with the change.
Note You need to log in before you can comment on or make changes to this bug.