[Bug] Strimzi operator not working via subscription inside openshift-ci cluster.

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Have a new openshift 4.5.x cluster created in openshift-ci (possibly any fresh openshift 4.5.x cluster)
2. Create a subscription to the strimzi operator – here is what our subscription looks like

spec:
  channel: stable
  name: strimzi-kafka-operator
  source: community-operators
  sourceNamespace: openshift-marketplace

Expected behavior The strimzi operator should be up and running in the openshift-operators namespace/project.

Actual behavior The strimzi operator is NOT up and running. The following snippet comes from the csv in the openshift-operators project.

  - group: ""
    kind: ServiceAccount
    message: Service account does not exist
    name: strimzi-cluster-operator
    status: NotPresent
    version: v1

Environment (please complete the following information):

• Strimzi version: [e.g. master, v0.20.0]
• Installation method: [e.g. subscription via OLM]
• Kubernetes cluster: [e.g. OpenShift 4.5]
• Infrastructure: [e.g. Openshift-ci cluster]

YAML files and logs

Attach or copy paste the custom resources you used to deploy the Kafka cluster and the relevant YAMLs created by the Cluster Operator. Attach or copy and paste also the relevant logs.

To easily collect all YAMLs and logs, you can use our report script which will automatically collect all files and prepare a ZIP archive which can be easily attached to this issue. The usage of this script is: ./report.sh [--namespace <string>] [--cluster <string>]

Additional context This problem just started for us during our Nightly openshift-ci run on Friday October 30. Prior to that, it was working well.

[i-sabo]

We’re also having an issue getting it to work on our OCP 4.6.21 cluster. We’re seeing the exact same behavior as @crobby and @kvijai82. It worked until recently, last week, and then any fresh install or upgrade we wanted to do was stopped by the service account not being created.

If we try to create the ServiceAccount manually, it says that it doesn’t have the required policies. Any help appreciated, thanks!

[scholzj]

PS: There is a dedicated channel with 0.19 which might get you unblocked if it is in any way related to 0.20.0. But obviously we should ideally make sure even the 0.20 works.