Cluster upgrade stuck with failed to update OS to quay.io in RHOCP4

Solution Verified - Updated -

Issue

  • Cluster upgrade stuck with the worker MachineConfigPool (MCP) reporting the below error:

        Reason:
        Status:                True
        Type:                  Updating
        Last Transition Time:  2025-07-13T15:23:49Z
        Message:               Node <node_name> is reporting: "failed to update OS to quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ad2174094abfb7182f223f9651d9929899a7ed5ceacf3c4eaad5c89eae687f39 : error running rpm-ostree rebase --experimental ostree-unverified-registry:quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ad2174094abfb7182f223f9651d9929899a7ed5ceacf3c4eaad5c89eae687f39: \x1b[0m\x1b[31merror: \x1b[0mImporting: proxy failure: remote error: read tcp 10.XX.XX.XX:38778->10.YY.YY.YY:8080: read: connection reset by peer and client error: Layer sha256:a233fe07bac5afca6f5bfaaec7e60bca65dfc8cd5495f2e6c9b9e177558916bc: unexpected end of file\n: exit status 1"
        Reason:                1 nodes are reporting degraded status on sync
        Status:                True
        Type:                  NodeDegraded
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 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