OpenShift upgrade to 4.13 is getting stuck with 'Child process stopped by signal 0'

Solution Verified - Updated -

Issue

  • Nodes are degraded after failing to run rpm-ostree rebase command due to Child process stopped by signal 0 after initiating the upgrade to RHOCP 4.13
Degraded Machine: <Node name> and Degraded Reason: failed to update OS to quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:888eda510e3c80bca8a43a939880543a0789e42cc1732c442c532d4575bb9692 : error running rpm-ostree rebase --experimental ostree-unverified-registry:quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:888eda510e3c80bca8a43a939880543a0789e42cc1732c442c532d4575bb9692: ESC[0mESC[31merror: ESC[0mSanity-checking final rootfs: bwrap(/usr/bin/true): Child process stopped by signal 0

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.13.z
  • IBM Power 8
  • Red Hat Virtualization, OpenShift Virtualization, VMWare ESXi or vSphere, Microsoft Hyper-V

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