Local storage operator can be installed on 4.3.0-0.nightly-2020-02-05-220314 $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.3.0-0.nightly-2020-02-05-220314 True False 100m Cluster version is 4.3.0-0.nightly-2020-02-05-220314 $ oc get csv -n local-storage NAME DISPLAY VERSION REPLACES PHASE local-storage-operator.4.3.1-202002051501 Local Storage 4.3.1-202002051501 Succeeded $ oc get all -n local-storage NAME READY STATUS RESTARTS AGE pod/local-storage-operator-6988478585-qqph6 1/1 Running 0 6m25s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/local-storage-operator ClusterIP 172.30.200.218 <none> 60000/TCP 6m17s NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/local-storage-operator 1/1 1 1 11m NAME DESIRED CURRENT READY AGE replicaset.apps/local-storage-operator-6988478585 1 1 1 6m29s
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, 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/RHBA-2020:0492