OpenShift Container Platform 4 - update is stuck as MachineConfigOperator is unable to drain OpenShift - Node

Solution Verified - Updated -

Issue

  • The OpenShift 4 update got stuck with the below message. If we force removal of such router pods the upgrade continues but gets stuck on the next node.

    5 tries: [error when evicting pods/"router-default-bb5b977bf-w2hm9" -n "openshift-ingress": global timeout reached: 1m30s, error when evicting pods/"router-default-bb5b977bf-w2hm9" -n "openshift-ingress": global timeout reached: 1m30s]

  • OpenShift 4 update is stuck as router pod is preventing Node from being evicted.

Environment

  • Red Hat OpenShift Container Platform (OCP) 4

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