RHBA-2020:3334 - Bug Fix Advisory

标题

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

描述

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.4.17. See the following advisory for the RPM packages for this
release:

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

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

This update fixes the following bugs among others:

• Previously, metadata featured on the CSV was not being ported using the `packagemanifests` type. Because of this, the OperatorHub UI was unable to filter Operators based on `packagemanifests` keywords. This bug has been fixed, and OperatorHub now has access to the following CSV information available in the package manifest:
• Keywords
• Maturity
• NativeAPIs
• MinKubeVersion
• RelatedImages
• Links
• Maintainers

The OperatorHub UI is now able to filter based on the CSV metadata. (BZ#1821274)

• Previously, the UID range allocation was never updated when a project was removed from the cluster. Restarting the kube-controller-manager Pod was the only way to trigger the repair procedure, which was clearing the range. A high project turnover could potentially exhaust the UID range on a cluster if this process was repeated many times. This bug is fixed fixed by periodically running the repair job automatically, which does not require additional kube-controller-manager restarts and ensures the UID range allocation is not exhausted. (BZ#1858800)
• Previously, intermittent availability issues with the API server could lead to intermittent issues with the OpenShift Controller Manager Operator retrieving deployments. Failure to retrieve a deployment sometimes caused the Operator to panic. With this release, checks have been added to handle and report this error condition, and to retry the operation. The Operator now properly handles intermittent issues retrieving deployments from the API server. (BZ#1861874)
• Due to a bug in the FeatureGate upgrade logic, the CVO was marking the cluster as not upgradeable to the next minor version when the LatencySensitive FeatureGate was in use. This bug has been fixed so minor version upgrades are no longer blocked. To work around this bug from previous releases, you must upgrade to a version that has this bug fixed. (BZ#1863076)

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

The image digest is
sha256:624e84b5d22cb865ee1be32aa6e3feea99917c6081f7a9c5b1185fc9934d23f3

(For s390x architecture)

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

The image digest is
sha256:0b52b50936e7ce8e0169848ace57cfd9cbfdf878b4e7788c7f531c77f78d6a3b

(For ppc64le architecture)

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

The image digest is
sha256:186ddd254863b3448dc22c332c0a9d07b6c043ab083305a59f96121719dde17c

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

解决方案

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

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

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

受影响的产品

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

修复

• BZ - 1821274 - OperatorHub filtering keyword limits
• BZ - 1824429 - Create button is disabled on Dev console when deploy image by searching digest image for container
• BZ - 1855878 - [4.4.z] Network Dispatcher long hostname character count is incorrect
• BZ - 1855895 - Egress Router pod is stuck in Init:CrashLoopBackOff
• BZ - 1858800 - rangeallocations.data is never updated when a project is removed
• BZ - 1860830 - After upgrading to 4.3.28 customer observed mistmatch between node labels (region=CanadaCentral) and pv affinity (region=canadacentral)
• BZ - 1861850 - [ci][sig-scheduling] SchedulerPriorities [Serial] Pod should be scheduled to node that don't match the PodAntiAffinity terms
• BZ - 1861874 - Nodes going notReady because of unknown Reason
• BZ - 1862113 - [4.4.z] update boot images to address CVE-2020-10713
• BZ - 1862171 - Pods cannot access the /config/master API endpoint: csrapprover: timed out waiting for the condition
• BZ - 1863076 - Cannot upgrade a cluster when adding Performance Profile Operator
• BZ - 1866099 - CI: make sure GCP UPI is using steps for PRs

CVE

• CVE-2019-11756
• CVE-2019-17006
• CVE-2019-17023
• CVE-2020-12402

参考

(none)