RHBA-2020:3180: OpenShift Container Platform 4.3.31 bug fix update

First published: Wed Aug 05 2020(Updated: )

Red Hat OpenShift Container Platform is Red Hat's cloud computing<br>Kubernetes application platform solution designed for on-premise or private<br>cloud deployments.<br>This advisory contains the container images for Red Hat OpenShift Container<br>Platform 4.3.31. See the following advisory for the RPM packages for this<br>release:<br><a href="https://access.redhat.com/errata/RHBA-2020:3179" target="_blank">https://access.redhat.com/errata/RHBA-2020:3179</a> Space precludes documenting all of the container images in this advisory.<br>See the following Release Notes documentation, which will be updated<br>shortly for this release, for details about these changes:<br><a href="https://docs.openshift.com/container-platform/4.3/release_notes/ocp-4-3-release-notes.html" target="_blank">https://docs.openshift.com/container-platform/4.3/release_notes/ocp-4-3-release-notes.html</a> This update fixes the following bugs among others:<br><li> 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)</li> <li> 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)</li> <li> 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)</li> <li> 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)</li> You may download the oc tool and use it to inspect release image metadata<br>as follows:<br>(For x86_64 architecture)<br>$ oc adm release info<br>quay.io/openshift-release-dev/ocp-release:4.3.31-x86_64<br>The image digest is<br>sha256:6395ddd44276c4a1d760c77f9f5d8dabf302df7b84afd7b3147c97bdf268ab0f<br>(For s390x architecture)<br>$ oc adm release info<br>quay.io/openshift-release-dev/ocp-release:4.3.31-s390x<br>The image digest is<br>sha256:a683c505ee50307fc8b7648891073fa050cf5bf7fad4f450162f0575922c0828<br>(For ppc64le architecture)<br>$ oc adm release info<br>quay.io/openshift-release-dev/ocp-release:4.3.31-ppc64le<br>The image digest is<br>sha256:72672afb691af66dd2027c2c3e674546e051e75f88f9cbe71ff7594243797a16<br>All OpenShift Container Platform 4.3 users are advised to upgrade to these<br>updated packages and images when they are available in the appropriate<br>release channel. To check for available updates, use the OpenShift Console<br>or the CLI oc command. Instructions for upgrading a cluster are available<br>at<br><a href="https://docs.openshift.com/container-platform/4.3/updating/updating-cluster-between-minor.html#understanding-upgrade-channels_updating-cluster-between-minor." target="_blank">https://docs.openshift.com/container-platform/4.3/updating/updating-cluster-between-minor.html#understanding-upgrade-channels_updating-cluster-between-minor.</a>

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

• collector/redhat-errata
• anchor-id/RHBA-2020:3180
• agent/description
• agent/event
• agent/first-publish-date
• agent/last-modified-date
• agent/references
• agent/remedy
• agent/severity
• agent/softwarecombine
• agent/tags
• agent/title
• agent/type