Description of problem (please be detailed as possible and provide log
snippests):

Following the docs (https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.5/html/deploying_openshift_container_storage_on_vmware_vsphere/deploy-using-local-storage-devices-vmware#installing-openshift-container-storage-operator-using-the-operator-hub_local-storage)

I have a 4.6.6 OCP cluster installed on vsphere 6.7. I also tried this with OCP 4.6.4. 
3 masters each with 4 cpu, 16GB mem, 120GB disk. 
3 workers each with 16 cpu, 48GB mem, 120GB disk

1. Added hard drives to each of the workers. 450GB each using SSD. 

2. Labeled worker nodes: oc label nodes <NodeNames> cluster.ocs.openshift.io/openshift-storage=''

3. Install OCS via operator. Version 4.5.2. Took defaults. openshift-storage ns not created yet. Checked box for cluster monitoring of the ns. Install successful.

4. Install local storage operator. Version 4.6.0-202011181111.p0. Took defaults. Did not create local-storage ns as docs say. Operator creates openshift-local-storage ns. Install successful.

*note docs say: The Local Storage Operator version must match the Red Hat OpenShift Container Platform version in order to have the Local Storage Operator fully supported with Red Hat OpenShift Container Storage. The Local Storage Operator does not get upgraded when Red Hat OpenShift Container Platform is upgraded.

So I should be able to use LSO 4.5, but it is not an option in the operator hub.

5. Found the storage devices (used DeamonSet):
oc apply -f https://raw.githubusercontent.com/dmoessne/ocs-disk-gather/master/ocs-disk-gatherer.yaml

kubectl logs --selector name=ocs-disk-gatherer --tail=-1 --since=10m --namespace default
          # NODE:ocp4-8shdf-worker3
          # sda : 120G
        - /dev/disk/by-id/scsi-36000c29c642b6968c93f4d5debccf016
          # sdb : 450G
        - /dev/disk/by-id/scsi-36000c29192fe04ec1d3de4a673f8fa76
 -------------------------------------------
          # NODE:ocp4-8shdf-worker2
          # sda : 120G
        - /dev/disk/by-id/scsi-36000c29c642b6968c93f4d5debccf016
          # sdb : 450G
        - /dev/disk/by-id/scsi-36000c294140d074b5cf9dd1cfd4abce8
 -------------------------------------------
          # NODE:ocp4-8shdf-worker1
          # sda : 120G
        - /dev/disk/by-id/scsi-36000c29c642b6968c93f4d5debccf016
          # sdb : 450G
        - /dev/disk/by-id/scsi-36000c29f014f7415f0cdf1de81eb8411
 -------------------------------------------

Created local volume CR:
apiVersion: local.storage.openshift.io/v1
kind: LocalVolume
metadata:
  name: local-block
  namespace: openshift-local-storage
  labels:
    app: ocs-storagecluster
spec:
  nodeSelector:
    nodeSelectorTerms:
    - matchExpressions:
        - key: cluster.ocs.openshift.io/openshift-storage
          operator: In
          values:
          - ""
  storageClassDevices:
    - storageClassName: localblock
      volumeMode: Block
      devicePaths:
        - /dev/disk/by-id/scsi-36000c29192fe04ec1d3de4a673f8fa76
        - /dev/disk/by-id/scsi-36000c294140d074b5cf9dd1cfd4abce8
        - /dev/disk/by-id/scsi-36000c29f014f7415f0cdf1de81eb8411

oc apply -f local-block.yaml

oc get sc | grep localblock
localblock       kubernetes.io/no-provisioner   Delete          WaitForFirstConsumer   false                  6m44

oc get pv
NAME                CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS      CLAIM   STORAGECLASS   REASON   AGE
local-pv-7b5a58bc   450Gi      RWO            Delete           Available           localblock              6m45s
local-pv-822c438f   450Gi      RWO            Delete           Available           localblock              6m45s
local-pv-e1ad8bd2   450Gi      RWO            Delete           Available           localblock              6m43s

6. Create service that uses local block storage in OCS
Internal mode: localblock storageclass is not presented.
Internal - attached devices: localblock storage class is present, but I get an error that says Minimum Node Requirement - The OCS Storage cluster require (sp) a minimum of 3 nodes for the initial deployment. Please choose a different stirage class or create a new volume set that matches the minimum node requirement. 

I've tried creating a new volume set, and that doesn't work either. 


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)? Yes. This use case does not work. 


Is there any workaround available to the best of your knowledge? I'm told I can do it via CLI, but if it's in the gui, it should work.


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


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:
1.
2.
3.


Actual results:


Expected results:


Additional info: