RHBA-2020:3180: OpenShift Container Platform 4.3.31 bug fix update
Red Hat OpenShift Container Platform is Red Hat's cloud computingKubernetes application platform solution designed for on-premise or privatecloud deployments.This advisory contains the container images for Red Hat OpenShift ContainerPlatform 4.3.31. See the following advisory for the RPM packages for thisrelease: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 updatedshortly for this release, for details about these changes:https://docs.openshift.com/container-platform/4.3/releasenotes/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 INITIALCLUSTER unless the node that commands were executed on was listed first in INITIALCLUSTER. 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 metadataas follows:(For x8664 architecture)$ oc adm release infoquay.io/openshift-release-dev/ocp-release:4.3.31-x8664The image digest issha256:6395ddd44276c4a1d760c77f9f5d8dabf302df7b84afd7b3147c97bdf268ab0f(For s390x architecture)$ oc adm release infoquay.io/openshift-release-dev/ocp-release:4.3.31-s390xThe image digest issha256:a683c505ee50307fc8b7648891073fa050cf5bf7fad4f450162f0575922c0828(For ppc64le architecture)$ oc adm release infoquay.io/openshift-release-dev/ocp-release:4.3.31-ppc64leThe image digest issha256:72672afb691af66dd2027c2c3e674546e051e75f88f9cbe71ff7594243797a16All OpenShift Container Platform 4.3 users are advised to upgrade to theseupdated packages and images when they are available in the appropriaterelease channel. To check for available updates, use the OpenShift Consoleor the CLI oc command. Instructions for upgrading a cluster are availableathttps://docs.openshift.com/container-platform/4.3/updating/updating-cluster-between-minor.html#understanding-upgrade-channelsupdating-cluster-between-minor.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHBA-2020:3180?
The severity of RHBA-2020:3180 is classified as important.
How do I fix RHBA-2020:3180?
To fix RHBA-2020:3180, update to Red Hat OpenShift Container Platform 4.3.31 or later.
What vulnerabilities are addressed in RHBA-2020:3180?
RHBA-2020:3180 addresses multiple issues that impact the stability and security of Red Hat OpenShift.
Is RHBA-2020:3180 applicable to all Red Hat OpenShift users?
RHBA-2020:3180 is specifically applicable to users of Red Hat OpenShift Container Platform version 4.3.31.
Where can I find more details about RHBA-2020:3180?
More details about RHBA-2020:3180 can typically be found in the associated Red Hat advisory.