Description of problem: AMQ-stream operator installation is failing while a non cluster-admin user trying to install the operator. Could see below error in operator status. ~~~ conditions: - lastTransitionTime: "2021-01-05T14:05:21Z" message: all available catalogsources are healthy reason: AllCatalogSourcesHealthy status: "False" type: CatalogSourcesUnhealthy - lastTransitionTime: "2021-01-05T14:24:22Z" reason: InstallComponentFailed status: "True" type: InstallPlanFailed currentCSV: amqstreams.v1.6.0 catalogSources: - redhat-operators conditions: - lastTransitionTime: "2021-01-05T14:05:20Z" lastUpdateTime: "2021-01-05T14:31:06Z" message: 'customresourcedefinitions.apiextensions.k8s.io is forbidden: User "system:serviceaccount:scoped:operator-installer" cannot create resource "customresourcedefinitions" in API group "apiextensions.k8s.io" at the cluster scope' reason: InstallComponentFailed status: "False" type: Installed phase: Failed plan: - resolving: amqstreams.v1.6.0 resource: group: operators.coreos.com kind: ClusterServiceVersion ~~~ In the document[1] it has been mentioned that cluster-admin permission should not be granted to service account mentioned in operator group resource but looking at the error message it seems a clusterrole must be required to get past this error. [1] - https://docs.openshift.com/container-platform/4.5/operators/admin/olm-creating-policy.html#olm-policy-understanding_olm-creating-policy Version-Release number of selected component (if applicable): OpenShift 4.5 How reproducible: Always Steps to Reproduce: 1. Follow document[1] to let a non cluster-admin install operators from oOperatorhub. 2. Try to install AMQ stream operator 3. Actual results: Operator installation is failing with a non cluster-admin user Expected results: Non cluster-admin user should be able to install operator by following instructions mentioned in document[1]. Additional info: PFA
This is a known issue being tracked by https://bugzilla.redhat.com/show_bug.cgi?id=1913085. Closing this out as a duplicate *** This bug has been marked as a duplicate of bug 1913085 ***