Description of problem (please be detailed as possible and provide log snippests): ODF LVM Operator filters removable devices that I would like to use. Please see further details on this Github issue https://github.com/red-hat-storage/lvm-operator/issues/109 Can the commit in that issue be back ported to the `release-4.10` branch? Version of all relevant components (if applicable): OpenShift 4.10.11 ODF LVM Operator stable-4.10 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Product is not usable on my hardware setup. Is there any workaround available to the best of your knowledge? Installing from the `main` branch but I would rather use an OLM release. 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 with disks that report as removable. Can this issue reproduce from the UI? N/A If this is a regression, please provide more details to justify this: Steps to Reproduce: See github issue linked above. Actual results: Operator does not use empty disks and stays in init phase. Expected results: Operator uses all empty disk in server. Additional info:
This has been fixed in 4.11 and it would be a simple matter to backport this to 4.10.z if PM and QE agree.
Verified
As we don't have env regression was run
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.11.0 security, enhancement, & bugfix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:6156