In order to land the fix for BZ#1969998 (and the follow-ons) as part of OCP 4.9, we needed to tag a build of `container-selinux` so that it would show up in the RHAOS plashets and be consumed by RHCOS. Since then, the `container-selinux` build shipped as part of https://access.redhat.com/errata/RHBA-2021:3661 and no longer needs to come from the RHAOS plashets. This bug is merely paperwork to allow a backport of the change to the `master` branch of `openshift/os` into the `release-4.9` branch.
To verify this BZ, inspect the build logs for RHCOS and ensure the following: - container-selinux-2.167.0-1 or newer is included - container-selinux comes from rhel8-appstream repo
There is no way to verify which repo a package came from. I just verified the PR in the manifest has container-selinux no longer pulling from `rhel-8-server-ose`. I tried to check the jenkins log of the compose build but those are blown away 410.84.202110081440-0 [core@localhost ~]$ sudo rpm-ostree status State: idle Deployments: ● ostree://67be3786510771cc550aa4be162f2b45cb796e4340755d7a67fa4720aa10e9ba Version: 410.84.202110081440-0 (2021-10-08T14:43:28Z) [core@localhost ~]$ rpm -q container-selinux container-selinux-2.167.0-1.module+el8.4.0+12646+b6fd1bdf.noarch
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 (Moderate: OpenShift Container Platform 4.10.3 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:0056