ibm-cem-brokers pod fails to start

The ibm-cem-brokers pod fails to start due to kafka topic issues.

Problem

When deploying the offering in your production environment, the ibm-cem-brokers pod does not fully start with one of the following log error messages:
  • Failed to fetch existing topics
  • Failed to initialize topics

Resolution

To check the log errors, first run the following command:
oc get pods | grep broker
The pod name is returned, as in the following example:
m242-ibm-cem-brokers-74dfd57645-2knvb 1/1 Running 0 5d17h
Check the log errors with the pod name, as in the following example:
oc logs po/m242-ibm-cem-brokers-74dfd57645-2knvb
If any of the topic errors are displayed, run the following command to restart the DNS:
oc delete pods --all -n openshift-dns
Draft comment: LOUISERoberts
#4658 Needs triage/work