kube-controller-manager-recovery-controller container crashing with conflicting port

Solution In Progress - Updated -

Issue

  • After upgrading to 4.5.3 in ocp clusters, the kube-controller-manager operator is in a degraded state with the following StaticPods_Error
StaticPodsDegraded: pod/kube-controller-manager-ocp4-25f6n-master-2 container "kube-controller-manager-recovery-controller" is not ready: CrashLoopBackOff: back-off 5m0s restarting failed container=kube-controller-manager-recovery-controller pod=kube-controller-manager-ocp4-25f6n-master-2_openshift-kube-controller-manager(2b5ff4ae86d1763793ace6b7adb77767) StaticPodsDegraded: pod/kube-controller-manager-ocp4-25f6n-master-2 container "kube-controller-manager-recovery-controller" is waiting: CrashLoopBackOff: back-off 5m0s restarting failed container=kube-controller-manager-recovery-controller pod=kube-controller-manager-ocp4-25f6n-master-2_openshift-kube-controller-manager(2b5ff4ae86d1763793ace6b7adb77767) StaticPodsDegraded: pod/kube-controller-manager-ocp4-25f6n-master-0 container "kube-controller-manager-recovery-controller" is not ready: CrashLoopBackOff: back-off 5m0s restarting failed container=kube-controller-manager-recovery-controller pod=kube-controller-manager-ocp4-25f6n-master-0_openshift-kube-controller-manager(2b5ff4ae86d1763793ace6b7adb77767) StaticPodsDegraded: pod/kube-controller-manager-ocp4-25f6n-master-0 container "kube-controller-manager-recovery-controller" is waiting: CrashLoopBackOff: back-off 5m0s restarting failed container=kube-controller-manager-recovery-controller pod=kube-controller-manager-ocp4-25f6n-master-0_openshift-kube-controller-manager(2b5ff4ae86d1763793ace6b7adb77767)

Environment

  • Red Hat OpenShift Container Platform
    • 4.5

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