RHBA-2021:0821 - Bug Fix Advisory

Topic

Red Hat OpenShift Container Platform release 4.7.3 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.7.3. See the following advisory for the RPM packages for this
release:

https://access.redhat.com/errata/RHBA-2021:0822

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.7/release_notes/ocp-4-7-release-notes.html

This update fixes the following bugs among others:

• Due to iptables rewriting rules, clients that used a fixed source port to connect to a service via both the service IP and a pod IP might have encountered problems with port conflicts. With this update, an additional OVS rule is inserted to notice when port conflicts occur and to do an extra SNAT to avoid said conflicts. As a result, there are no longer port conflicts when connecting to a service. (BZ#1936920)
• Previously, the fix for BZ#1932401 overrode the default Go HTTP client transport. Consequently, cluster-wide proxy settings were not plumbed through to the Ingress Operator pod, which resulted in the failure of canary checks on a cluster with a cluster-wide egress proxy. This update explicitly sets proxy settings in the canary client's HTTP transport. As a result, canary checks work with all cluster-wide proxies. (BZ#1936093)
• Previously, the `growpart` script did not consider in-place LUKS rootfs reprovisioning as `requiring growing`. Consequently, machines which enabled in-place LUKs encryption ended up with rootfs too small. With this update, the `growpart` script (now `ignition-ostree-growfs`) considers in-place LUKS rootfs reprovisioning as `requiring growing`. As a result, machines which enable in-place LUKs encryption have rootfs that take up all available space. (BZ#1934863)
• Previously, the canary DaemonSet did not specify a node selector, so it used the default node selector for the canary namespace. Consequently, the canary DaemonSet could not schedule to infra nodes and in some cases would throw alerts. This update explicitly schedules the canary DaemonSet to infra nodes and tolerates tainted infra nodes. This allows the canary DaemonSet to safely roll out to worker and infra nodes without issues or alerts. (BZ#1934940)

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.6.20-x86_64

The image digest is
sha256:edb08aaadf32f0b2e800f7e29e6f7a1b225211514401e92601ba94a971dec838

(For s390x architecture)

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

The image digest is
sha256:1275ec59cc465729c9a18facaa471e013a4ad86a1bec5236b4169191922f7b5c

(For ppc64le architecture)

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

The image digest is
sha256:3be77380237c49f3583772c3e8d27b0ce97c60d9dadf90f34aaaa2097b98e96c

All OpenShift Container Platform 4.7 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.7/updating/updating-cluster-between-minor.html#understanding-upgrade-channels_updating-cluster-between-minor.

Solution

For OpenShift Container Platform 4.7 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.7/release_notes/ocp-4-7-release-notes.html

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

Affected Products

• Red Hat OpenShift Container Platform 4.7 for RHEL 8 x86_64
• Red Hat OpenShift Container Platform for Power 4.7 for RHEL 8 ppc64le
• Red Hat OpenShift Container Platform for IBM Z and LinuxONE 4.7 for RHEL 8 s390x

Fixes

• BZ - 1925475 - high CPU usage fails ingress controller
• BZ - 1926795 - CannotRetrieveUpdates alerts on Critical severity
• BZ - 1926876 - [4.7]"500 Internal Error" for prometheus route in https_proxy cluster
• BZ - 1927256 - [oVirt] consume K8S 1.20 packages
• BZ - 1928028 - kuryr-cni binds to wrong interface on machine with two interfaces
• BZ - 1928029 - kuryr-controller in crash loop if IP is removed from secondary interfaces
• BZ - 1929904 - ClusterServiceVersion property inference does not infer package and version
• BZ - 1930017 - [kuryr] Egress network policy with namespaceSelector in Kuryr behaves differently than in OVN-Kubernetes
• BZ - 1931615 - [4.7] Fresh UPI install on BM with bonding using OVN Kubernetes fails
• BZ - 1931702 - remove periodic log within kubelet
• BZ - 1931745 - Backport upstream patch 98956 for pod terminations
• BZ - 1931765 - LocalVolumeSet: PV is created on disk belonging to other provisioner
• BZ - 1932820 - kube-apiserver-availability.rules are failing evaluation
• BZ - 1932860 - recycler-pod template should not be in kubelet static manifests directory
• BZ - 1933094 - activeDeadlineSeconds DeadlineExceeded does not show terminated container statuses
• BZ - 1933368 - machine-config ClusterOperator claims level while control-plane still updating
• BZ - 1933659 - Cinder CSI driver is not able to mount volumes under heavier load
• BZ - 1933695 - Placeholder bug for OCP 4.7.0 metadata release
• BZ - 1934724 - Bundles skipped via the `skips` field cannot be pinned
• BZ - 1934863 - [4.7.z] rootfs too small when enabling NBDE
• BZ - 1934904 - Canary daemonset uses default node selector
• BZ - 1935473 - Cluster unstable replacing an unhealthy etcd member
• BZ - 1935805 - Documentation Links in OKD Web Console are not Working
• BZ - 1935891 - Canary client should perform canary probes explicitly over HTTPS (rather than redirect from HTTP)
• BZ - 1936093 - [AWS][Proxy] ingress reports degrade with CanaryChecksSucceeding=False in the cluster with proxy setting
• BZ - 1936334 - Updating multus-cni builder & base images to be consistent with ART
• BZ - 1936587 - Cluster DNS service caps TTLs too low and thus evicts from its cache too aggressively
• BZ - 1936920 - socket timeouts for webservice communication between pods
• BZ - 1937086 - Blank White page on Topology
• BZ - 1937170 - [sig-arch] Managed cluster should have no crashlooping pods in core namespaces over four minutes
• BZ - 1937238 - Ingress traffic performance drop due to NodePort services

CVEs

(none)

References

(none)