Cloning this Bug to OCS as we want to document it as a KNOWN issue till the OCP bug is fixed +++ This bug was initially created as a clone of Bug #1905622 +++ This bug was initially created as a copy of Bug #1899949 I am copying this bug because: Description of problem (please be detailed as possible and provide log snippests): For LSO deployments, the storage cluster creation UI only allows selecting disktype = ssd. On virtualized platforms like RHV/VMWare and on some cloud platforms - Azure/IBM Cloud, the disks are reported as rotational on the guest VMs, as the underlying storage is abstracted. Even though the underlying hardware is SSD, these virtual disks cannot be selected for OCS due to SSD disktype restriction. The disktype should be optional while creating the LVS. Version of all relevant components (if applicable): 4/6 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? User is unable to create cluster using documented flow Is there any workaround available to the best of your knowledge? Workaround is to create the LVS and StorageClass from the Local Storage Operator UI 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 If this is a regression, please provide more details to justify this: Steps to Reproduce: As described
Created attachment 1739970 [details] For ovirt - LSO deployments, the storage cluster creation UI now allows selecting HDD too disktype as SSD Verified it on ovirt platform OCP version 4.6.0-0.nightly-2020-12-16-180954 OCS Version - ocs-operator.v4.6.0-195.ci In LSO based OCS deployments, the storage cluster creation UI page, now showing the "All" option as default disk type selection and dropdown list allowing to select "HDD" disk type.
Closing the tracker bug as the OCP bug is fixed and the Note , refer comment#5, is removed from all the docs