Node degraded during cluster upgrade with the message "Error checking type of update image: failed to run command podman (6 tries): [timed out waiting for the condition, running podman pull -q --authfile /var/lib/kubelet/config.json failed"

Solution Verified - Updated -

Issue

  • During the Cluster upgrade from 4.11 to 4.12, nodes in MCP got degraded due to the below error.
- lastTransitionTime: '2023-07-07T03:07:01Z'
    message: 'Node master2.ocp.example.com is reporting: "Error checking type of update
      image: failed to run command podman (n tries): [timed out waiting for the condition,
      running podman pull -q --authfile /var/lib/kubelet/config.json   failed: Error:
      invalid reference format\n: exit status 125]"'
    reason: 1 nodes are reporting degraded status on sync
    status: 'True'
    type: NodeDegraded

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.12.z

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