Cluster-monitoring-operator pod rollout stuck with error message CreateContainerConfigError.

Solution In Progress - Updated -


  • During upgrade to Red Hat OpenShift Container Platform 4.6.x the CMO pod stuck with error message:
Pod openshift-monitoring/cluster-monitoring-operator-xxxxxx container kube-rbac-proxy has been in waiting state for longer than 1 hour.
Deployment openshift-monitoring/cluster-monitoring-operator has not matched the expected number of replicas for longer than 15 minutes.
Pod openshift-monitoring/cluster-monitoring-operator-xxxxxxx  has been in a non-ready state for longer than 15 minutes.
  • Another error reported is as follows.
Error: container has runAsNonRoot and image has non-numeric user (nobody), cannot verify user is non-root


  • Red Hat OpenShift Container Platform 4.6.8

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In