RHBA-2019:1766 - Bug Fix Advisory

Topic

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

Description

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

https://access.redhat.com/errata/RHBA-2019:1767

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

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

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

The image digest is sha256:aa955a9ec40e55e5d9c0203a995b398e8c1031473dae24ed405efe9a95b43186

All OpenShift Container Platform 4.1 users are advised to upgrade to these
updated packages and images.

Solution

Before applying this update, ensure all previously released errata
relevant to your system have been applied.

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

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

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

Affected Products

• Red Hat OpenShift Container Platform 4.1 for RHEL 7 x86_64

Fixes

• BZ - 1717535 - Networking details are missing for some deployment configs in web console overview
• BZ - 1717640 - clusteroperator/storage does not define any related resources
• BZ - 1719958 - oc get clusterversion does not list version when there is an error state on update
• BZ - 1720161 - Content is overlapping on Machine Configs page
• BZ - 1720270 - [4.1] TLS Keys Not Added to Registry Routes
• BZ - 1720677 - [Backport][OCP4.1] Fix panic in kube-proxy when iptables-save prints to stderr
• BZ - 1721146 - Node overview page shows incorrect metrics due to too wide selector
• BZ - 1722225 - Create route form incorrectly states that hostnames can't be changed
• BZ - 1722919 - Pin openshift dependencies (api, client-go, library-go and s2i) to appropriate 4.1 release branches
• BZ - 1723553 - oc delete of a static pod results in multiple attempts to re-create the mirror pod before succeeding
• BZ - 1723869 - Terminate custom resource watches when storage is destroyed
• BZ - 1723928 - Backport kubelet recovery script to 4.1.z
• BZ - 1724103 - version is not right for cluster_version{type="cluster"} after upgrade
• BZ - 1724784 - Unable to identify age of cluster in relation to current version via PromQL
• BZ - 1724833 - elasticsearch and clusterlogging CSV resources need cleanup
• BZ - 1726745 - Improve Samples Operator Test Reporting
• BZ - 1727308 - ca.crt is not set properly when creating identity providers in the web console
• BZ - 1729273 - During upgrade, node-tuning operator status rapidly alternates between new and old version
• BZ - 1729345 - Upgrade failure with "Marking Degraded due to: during bootstrap: unexpected on-disk state validating" error.

CVEs

• CVE-2019-10156
• CVE-2019-10160
• CVE-2019-12735

References

(none)