RHBA-2022:1022 - Bug Fix Advisory

Topic

Red Hat OpenShift Container Platform release 4.9.26 is now available with
updates to packages and images that fix several bugs.

Description

Red Hat OpenShift Container Platform is Red Hat's cloud computing
Kubernetes application platform solution designed for on-premise or private
cloud deployments.

This advisory contains the container images for Red Hat OpenShift Container
Platform 4.9.26. See the following advisory for the RPM packages for this
release:

https://access.redhat.com/errata/RHSA-2022:1021

Space precludes documenting all of the container images in this advisory.
See the following Release Notes documentation, which will be updated
shortly for this release, for details about these changes:

https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.html

You may download the oc tool and use it to inspect release image metadata
as follows:

(For x86_64 architecture)

$ oc adm release info
quay.io/openshift-release-dev/ocp-release:4.9.26-x86_64

The image digest is sha256:bb93e9a347b6acdcafff5acbf15010beb4ac25f14d3eea46d5dccf9d78f71aa0

(For s390x architecture)

$ oc adm release info
quay.io/openshift-release-dev/ocp-release:4.9.26-s390x

The image digest is sha256:5acf2d38364359297255c00524e105fd96812112c1bb2f3ca8b3836561b1f39

(For ppc64le architecture)

$ oc adm release info
quay.io/openshift-release-dev/ocp-release:4.9.26-ppc64le

The image digest is sha256:d9b63a2ef127b8ad8a2ea31ed95b61b656a2d90579d655b0c1e11ae59cb4bf1f

All OpenShift Container Platform 4.9 users are advised to upgrade to these
updated packages and images when they are available in the appropriate
release channel. To check for available updates, use the OpenShift Console
or the CLI oc command. Instructions for upgrading a cluster are available
at
https://docs.openshift.com/container-platform/4.9/updating/updating-cluster-cli.html

Solution

For OpenShift Container Platform 4.9 see the following documentation, which
will be updated shortly for this release, for important instructions on how
to upgrade your cluster and fully apply this asynchronous errata update:

https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.html

Details on how to access this content are available at
https://docs.openshift.com/container-platform/4.9/updating/updating-cluster-cli.html

Affected Products

• Red Hat OpenShift Container Platform 4.9 for RHEL 8 x86_64
• Red Hat OpenShift Container Platform for Power 4.9 for RHEL 8 ppc64le
• Red Hat OpenShift Container Platform for IBM Z and LinuxONE 4.9 for RHEL 8 s390x
• Red Hat OpenShift Container Platform for ARM 64 4.9 aarch64

Fixes

• BZ - 2021702 - optional operator conditions are confusing
• BZ - 2023614 - ERROR deleter could not get provisioner configmap
• BZ - 2030630 - 400 Bad Request error for some queries for the non admin user
• BZ - 2032125 - Cluster-version operator does not remove unrecognized volume mounts
• BZ - 2033712 - The Nodes section doesn't display the csr of the nodes that are trying to join the cluster
• BZ - 2045008 - update discovery burst to reflect lots of CRDs on openshift clusters
• BZ - 2055317 - POD DNS request times out when one of the master nodes fails
• BZ - 2057518 - Ingresscontroller LB scope change behaviour differs for different values of aws-load-balancer-internal annotation
• BZ - 2060080 - [4.9z] Network policies are not implemented or updated by OVN-Kubernetes
• BZ - 2060111 - ingress operator should report Upgradeable False to remind user before upgrade to 4.10 when Non-SAN certs are used
• BZ - 2063350 - RHEL8 Workers Need to Ensure libseccomp is up to date at install time
• BZ - 2064586 - Ingress Operator is not closing TCP connections.
• BZ - 2065302 - `oc debug node` does not meet compliance requirement
• BZ - 2065483 - AWS io2 machine fails due to no iops despite it being configured

CVEs

• CVE-2022-0711
• CVE-2022-25173
• CVE-2022-25174
• CVE-2022-25175
• CVE-2022-25176
• CVE-2022-25177
• CVE-2022-25178
• CVE-2022-25179
• CVE-2022-25180
• CVE-2022-25181
• CVE-2022-25182
• CVE-2022-25183
• CVE-2022-25184

References

(none)