Child process exited with code 1 during RHOCP cluster upgrade from 4.12.z to 4.13.z

Solution Verified - Updated -

Issue

  • During the cluster upgrade from version 4.12.z to 4.13.z, in the final step of updating the machine-config operator and applying machine-config, nodes enter a degraded state accompanied by the following error:

    unexpected on-disk state validating against rendered-worker-aa8ea7869b154c4f4057a9b525a468e7: expected target osImageURL \\\"quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:b97e5afdb73043727f78f09f6a6f369d07125d0306e9cc42eae519e4cb826736\\\", have \\\"quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:95d04bea30c295df64bbe8bd708552010b78bd21a22dc0f42df1e24d35e9d587\\\" (\\\"448d8cd88a474c1a4ef38f285a7c1cc30dc9421288fee56c187f739413c38867\\\"); possible root cause: error: Child process exited with code 1

NOTE The relevance of this KCS is limited to situations where nodes feature a custom machine configuration that defines a semodule. Refer to the 'Diagnosis' section in the document for steps to verify the occurrence of this issue.

Environment

  • Red Hat OpenShift Container Platform
    • 4.12.z (while upgrading to 4.13.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