Strimizi-Kafka-operator ends up "Unknown" status

[barryzhounb]

On OpenShift, striimizi Operator worked well for weeks, somehow when we want to create kafka cluster, it doesn't work. Then we uninstall Operator, and re-install Operator, now Strimizi-Kafka-operator ends up "Unknown" status.

OpenShoft version is 4.4.x, Strimizi-Kafka-operator version is seleccted as "stable".

Is there any way to fix it or troubleshooting it?

The following is Operator's yaml and CR status.

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  creationTimestamp: '2021-03-29T12:14:58Z'
  generation: 1
  name: strimzi-kafka-operator
  namespace: openshift-operators
  resourceVersion: '88845839'
  selfLink: >-
    /apis/operators.coreos.com/v1alpha1/namespaces/openshift-operators/subscriptions/strimzi-kafka-operator
  uid: b83cc4c6-1d29-46ac-a7f6-19e92059b518
spec:
  channel: stable
  installPlanApproval: Automatic
  name: strimzi-kafka-operator
  source: community-operators
  sourceNamespace: openshift-marketplace
  startingCSV: strimzi-cluster-operator.v0.22.1
status:
  catalogHealth:
    - catalogSourceRef:
        apiVersion: operators.coreos.com/v1alpha1
        kind: CatalogSource
        name: certified-operators
        namespace: openshift-marketplace
        resourceVersion: '88844716'
        uid: cfbf8e21-6d7b-46f5-8c63-0e3dfd17bfd0
      healthy: true
      lastUpdated: '2021-03-29T12:14:58Z'
    - catalogSourceRef:
        apiVersion: operators.coreos.com/v1alpha1
        kind: CatalogSource
        name: community-operators
        namespace: openshift-marketplace
        resourceVersion: '88844732'
        uid: d0c54e9e-2a49-4c05-b362-1cac1a6da11e
      healthy: true
      lastUpdated: '2021-03-29T12:14:58Z'
    - catalogSourceRef:
        apiVersion: operators.coreos.com/v1alpha1
        kind: CatalogSource
        name: ibm-operator-catalog
        namespace: openshift-marketplace
        resourceVersion: '88844799'
        uid: 83249661-d114-4fbe-a075-fdec6d72523c
      healthy: true
      lastUpdated: '2021-03-29T12:14:58Z'
    - catalogSourceRef:
        apiVersion: operators.coreos.com/v1alpha1
        kind: CatalogSource
        name: opencloud-operators
        namespace: openshift-marketplace
        resourceVersion: '88844781'
        uid: 9dd4c4fd-90f8-4d9a-8e4f-90efa7a09e07
      healthy: true
      lastUpdated: '2021-03-29T12:14:58Z'
    - catalogSourceRef:
        apiVersion: operators.coreos.com/v1alpha1
        kind: CatalogSource
        name: redhat-marketplace
        namespace: openshift-marketplace
        resourceVersion: '88844671'
        uid: fcd3bfaa-b5d1-4250-b4f6-8f8d6a4823c1
      healthy: true
      lastUpdated: '2021-03-29T12:14:58Z'
    - catalogSourceRef:
        apiVersion: operators.coreos.com/v1alpha1
        kind: CatalogSource
        name: redhat-operators
        namespace: openshift-marketplace
        resourceVersion: '88844678'
        uid: 07430e4e-5da1-4042-9715-e673892335aa
      healthy: true
      lastUpdated: '2021-03-29T12:14:58Z'
  conditions:
    - lastTransitionTime: '2021-03-29T12:14:58Z'
      message: all available catalogsources are healthy
      reason: AllCatalogSourcesHealthy
      status: 'False'
      type: CatalogSourcesUnhealthy
  lastUpdated: '2021-03-29T12:14:58Z'

[scholzj]

I think OpenShift 4.4 is too old (in this respect mainly the OLM component). I think it cannot handle the ConfigMap with logging. You should probably either try some older Strimzi version or upgrade your OCP cluster.