Description of problem:
In the oVirt cluster, cluster storage operator will not create storage class directly, so from this point, the stauts reports "DefaultStorageClassControllerAvailable: No default StorageClass for this platform" is correct, but the oVirt csi operator managed by CSO will create a default storage class, it makes this status looks a little of confusion.

Version-Release number of selected component (if applicable):
4.6.0-0.nightly-2020-08-26-010422

How reproducible:
Always

Steps to Reproduce:
1.Have an OCP46 cluster on oVirt
2.Check the CSO status
3.Check the storage class

Actual results:
$ oc get co storage -ojson |jq .status
{
  "conditions": [
    {
      "lastTransitionTime": "2020-08-26T01:40:46Z",
      "reason": "AsExpected",
      "status": "False",
      "type": "Degraded"
    },
    {
      "lastTransitionTime": "2020-08-26T01:55:37Z",
      "reason": "AsExpected",
      "status": "False",
      "type": "Progressing"
    },
    {
      "lastTransitionTime": "2020-08-26T01:55:37Z",
      "message": "DefaultStorageClassControllerAvailable: No default StorageClass for this platform",
      "reason": "AsExpected",
      "status": "True",
      "type": "Available"
    },
...

$ oc get sc
NAME                     PROVISIONER     RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
ovirt-csi-sc (default)   csi.ovirt.org   Delete          Immediate           false                  85m


Expected results:

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info: