RHBA-2021:0678 - Bug Fix Advisory

Topic

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

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

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:

• Previously, the SSH public key validation was not applied when using the `generate ISO` API. Consequently, malformed SSH public keys were accepted without returning an error, which would eventually cause failures during cluster installation. This update applies the same SSH public key when generating an ISO. As a result, a malformed SSH public key is now rejected with an error message. (BZ#1911803)
• Previously, exposing the default Ingress Controller via an external load balancer redirected all HTTP traffic to HTTPS. Consequently, canary endpoint checks performed by the Ingress Operator would fail, which would cause the Ingress cluster to become degraded. This update converts the cleartext canary route to an edge encrypted route. As a result, the canary route now works when non-secure traffic is redirected by the load balancer. (BZ#1932649)
• Previously, overlapping IPV6 subnets for different NICs would result in a failed deployment of the Keepalived configuration. For example:

`Interface A subnet: 1001:db8::/120`
`Interface B subnet: 1001:db8::f00/120`
`VIP address 1001:db8::64`

This update selects the NIC whose address is connected with the VIP address. As a result, the correct interface is selected for the Keepalived configuration. (BZ#1905233)

• Previously, CDI tests used the dev branch of CDI, but would fail on the latest dev version of CDI. This update locks the test environment to use a stable version of CDI, which allows CDI tests to pass. (BZ#1926830)
• The SR-IOV device plug-in does not allow VFIO devices on the nodes to be exposed as resources. This results in DPDK workloads being blocked on Intel devices. It is recommended that SR-IOV customers should not upgrade to OpenShift Container Platform 4.7 until this issue is fixed. (BZ#1930469)

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:93d68c88761c604448280d35367e7a253f1e05891a28d2ee4d99a4b474cf130f

(For s390x architecture)

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

The image digest is
sha256:25909322759eecb2227fa46c2c0c8f61df547e607e27de34d0e1ce293e53ef0d

(For ppc64le architecture)

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

The image digest is
sha256:5f88cbc6aa99ea99b231c502c21873ea09ee9a80154885c413ed3aa6f018396a

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 - 1905233 - Incorrect interface selection when creating keepalived configuration for IPv6
• BZ - 1911803 - [Assisted-4.6] [Staging] No BE validation for SSH key when generating an ISO
• BZ - 1915234 - [OCP on RHV] when choosing version to update channel, there is Ok button instead of Update button
• BZ - 1915694 - golden images - DV should not be created with WaitForFirstConsumer
• BZ - 1921413 - cluster version operator cycles terminating state waiting for leader election
• BZ - 1921909 - Enable STS Support for Image Registry
• BZ - 1925659 - Insights operator should not go degraded during upgrade
• BZ - 1925739 - cluster-etcd-operator is leaking transports
• BZ - 1925740 - GCP jobs exhaust zone listing query quota sometimes due to too many initializations of cloud provider in tests
• BZ - 1926830 - [e2e][automation] prow gating use unsupported CDI version
• BZ - 1927405 - [4.7z] OVS configuration service unable to clone NetworkManager's connections in the overlay FS
• BZ - 1928304 - hostname lookup delays when master node down
• BZ - 1929012 - API priority test case flaking in CI
• BZ - 1930357 - Darwin binary missing from mirror.openshift.com
• BZ - 1930469 - intel vfio devices are not expose as resources
• BZ - 1930490 - The operator-sdk version in mirror tarball in not sync with the release container
• BZ - 1930876 - The etcdInsufficientMembers alert fires incorrectly when any instance is down and not when quorum is lost
• BZ - 1932649 - Cluster Ingress Operator degrades if external LB redirects http to https because of new "canary" route

CVEs

• CVE-2020-6829
• CVE-2020-8625
• CVE-2020-12400
• CVE-2020-12403
• CVE-2020-12723
• CVE-2020-14351
• CVE-2020-25705
• CVE-2020-29661

References

(none)