RHBA-2020:3180 - Bug Fix Advisory

Topic

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

https://access.redhat.com/errata/RHBA-2020:3179

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

This update fixes the following bugs among others:

• Previously, it was inconvenient to push release images or referenced images from a local disk to a local repository because the `oc adm release mirror` command lacked `file://` support. Attempts to refer to an image on a local disk failed with an "invalid image reference" error. With this release, `oc adm release mirror` can use paths from `file://` successfully. (BZ#1806782)
• Previously, the `etcd-snapshot-restore.sh` script failed when trying to run with more than one member listed in `INITIAL_CLUSTER` unless the node that commands were executed on was listed first in `INITIAL_CLUSTER`. The issue has been resolved in this release. (BZ#1826021)
• Previously, controllers missed some `NotFound` errors and as a result were not aware of missing Pods. The issue has been resolved in this release. (BZ#1843877)
• During installation or upgrade, the `openshift-controller-manager` did not correctly report its progress condition. As a result, an installation or upgrade might fail. Now the Operator correctly reports its progress upon a successful installation or upgrade. (BZ#1854133)

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

The image digest is
sha256:6395ddd44276c4a1d760c77f9f5d8dabf302df7b84afd7b3147c97bdf268ab0f

(For s390x architecture)

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

The image digest is
sha256:a683c505ee50307fc8b7648891073fa050cf5bf7fad4f450162f0575922c0828

(For ppc64le architecture)

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

The image digest is
sha256:72672afb691af66dd2027c2c3e674546e051e75f88f9cbe71ff7594243797a16

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

Solution

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

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

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

Affected Products

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

Fixes

• BZ - 1785718 - support for ipv6
• BZ - 1806782 - Cannot mirror a local release to a remote registry
• BZ - 1815634 - [release-4.3] etcd: raft can stop before purge loop exists resulting in wal: file not found
• BZ - 1818806 - Default openshift install requests too many CPU resources to install all components, requests of components on cluster are wrong
• BZ - 1825722 - click "Machine Config Pools" after mcp creation making page crash
• BZ - 1826021 - [4.3] etcd-snapshot-restore.sh fails due to "Error: snapshot restore requires exactly one argument"
• BZ - 1843877 - daemonset, deployment, and replicaset status can permafail
• BZ - 1845494 - File restoration doesn't work as expected when it is not owned by an rpm but available in /usr/etc/
• BZ - 1846358 - Machine Config Daemon Daemon Set does not set universal Toleration (and therefore gets booted if taints are set on a node)
• BZ - 1849152 - operator-registry base image used for disconnected catalogs does not have permission to migrate databases added via `oc adm catalog build`
• BZ - 1849153 - openshift-marketplace: Pods found with invalid container images not present in release payload (v2)
• BZ - 1851606 - remove use of upstream client plugin pipeline from openshift build e2e
• BZ - 1853171 - system:serviceaccount:kube-system:cloud-provider cannot create resource events
• BZ - 1854133 - failed to initialize the cluster: Cluster operator openshift-controller-manager is still updating (operator version not set)
• BZ - 1854997 - Cannot access logs in kibana with the managed deployment orchestrated by the cluster logging operator
• BZ - 1855072 - Elasticsearch shows UnsupportedOperationException seccomp unavailable ppc64le architecture unsupported [4.3]
• BZ - 1855304 - Machine Config operator parses kubelet.conf reducing usability.
• BZ - 1856125 - OLM Not Respecting Default Channel in OCP 4.5
• BZ - 1857159 - Placeholder bug for OCP 4.3.z image release
• BZ - 1859308 - Libvirt machine controller causes hypervisor URI to hang
• BZ - 1859748 - [4.3] lib-bucket-provisioner v2 upgrade attempt to install both v1 and v2

CVEs

• CVE-2020-9283
• CVE-2020-12049
• CVE-2020-14556
• CVE-2020-14562
• CVE-2020-14573
• CVE-2020-14577
• CVE-2020-14578
• CVE-2020-14579
• CVE-2020-14583
• CVE-2020-14593
• CVE-2020-14621

References

(none)