When installing the operator, OLM GUI should strongly suggest "openshift-aws-ebs-csi-driver-operator" namespace. We don't want users to use other namespaces, because the operator will be installed by default in a next OCP release and thus the old operator should be easy to find and "adopt" during update to that OCP release.
Verified with: # oc get csv -n openshift-aws-ebs-csi-driver-operator NAME DISPLAY VERSION REPLACES PHASE aws-ebs-csi-driver-operator.v4.5.0 AWS EBS CSI Operator 4.5.0 Succeeded ose-aws-ebs-csi-driver-operator-bundle-container-v4.5-6 ose-aws-ebs-csi-driver-operator-container-v4.5-5
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:2409