Master controllers pods in CrashLoopBackOff state

Solution Verified - Updated -

Issue

  • 2 of 3 Master controllers pods in CrashLoopBackOff state
  • Master controller pod logs shows panic: interface conversion: interface {} is nil, not []interface {}
  • goroutine 160 [running]:github.com/openshift/origin/vendor/k8s.io/kubernetes/cmd/kube-controller-manager/app.applyOpenShiftConfigControllerArgs(0xc4207a29a0, 0xc421b46540, 0x1e17, 0x24f6)
  • Tried restarting the master-controllers but still controller pods going in CrashLoopBackOff state

Environment

  • OpenShift Container Platform
    • 3.11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content