This is a tracker bug to monitor the inclusion of any fixes from BZ#2058176 into RHCOS. +++ This bug was initially created as a clone of Bug #2058176 +++ See https://github.com/openshift/os/issues/666#issuecomment-1049494630 TL;DR For FCOS/RHCOS we mount the rootfs with a non-zero offset, and that change is needed in order to make it not racy. --- Additional comment from Micah Abbott on 2022-02-28 14:22:13 UTC --- Setting this to high severity as it is blocking the ability to properly test some ISO scenarios for RHCOS
This bug has been reported fixed in a new RHCOS build and is ready for QE verification. To mark the bug verified, set the Verified field to Tested. This bug will automatically move to MODIFIED once the fix has landed in a new bootimage.
Pre-verified [core@cosa-devsh ~]$ rpm-ostree status State: idle Deployments: * 28fcf965242328992056b4bcf039045c737f181de7cd95b6fa39e0812151d9dd Version: 411.86.202206281842-0 (2022-06-28T18:46:24Z) [core@cosa-devsh ~]$ rpm -q util-linux util-linux-2.32.1-35.el8.x86_64
The fix for this bug has landed in a bootimage bump, as tracked in bug 2093126 (now in status MODIFIED). Moving this bug to MODIFIED.
Verified on 4.11.0-0.nightly-2022-07-05-083948 $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.11.0-0.nightly-2022-07-05-083948 True False 29m Cluster version is 4.11.0-0.nightly-2022-07-05-083948 $ oc get nodes NAME STATUS ROLES AGE VERSION ci-ln-4kx6pgb-1d09d-wng42-master-0 Ready master 55m v1.24.0+2dd8bb1 ci-ln-4kx6pgb-1d09d-wng42-master-1 Ready master 59m v1.24.0+2dd8bb1 ci-ln-4kx6pgb-1d09d-wng42-master-2 Ready master 55m v1.24.0+2dd8bb1 ci-ln-4kx6pgb-1d09d-wng42-worker-centralus1-cvscz Ready worker 45m v1.24.0+2dd8bb1 ci-ln-4kx6pgb-1d09d-wng42-worker-centralus2-dsnc8 Ready worker 45m v1.24.0+2dd8bb1 ci-ln-4kx6pgb-1d09d-wng42-worker-centralus3-g5js6 Ready worker 45m v1.24.0+2dd8bb1 $ oc debug node/ci-ln-4kx6pgb-1d09d-wng42-master-0 -- chroot /host rpm-ostree status Starting pod/ci-ln-4kx6pgb-1d09d-wng42-master-0-debug ... To use host binaries, run `chroot /host` State: idle Deployments: * pivot://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:04b54950ce296d73746f22b66ff6c5484c37be78cb34aaf352338359112fa241 CustomOrigin: Managed by machine-config-operator Version: 411.86.202207011902-0 (2022-07-01T19:05:18Z) 0505ffc1c711903785f27570819e973f086f594a8daa3ec9dfe2a059586ac42f Version: 411.86.202206301504-0 (2022-06-30T15:08:01Z) Removing debug pod ... $ oc debug node/ci-ln-4kx6pgb-1d09d-wng42-master-0 -- chroot /host rpm -q util-linux To use host binaries, run `chroot /host` util-linux-2.32.1-35.el8.x86_64 Removing debug pod ...
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069