RHBA-2020:2589 - Bug Fix Advisory

Topic

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

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

This update fixes the following bugs among others:

• Previously, there was no suitable endpoint in the service catalog for Octavia. This caused destroying clusters on the Red Hat OpenStack Platform using installer-provisioned infrastructure to fail. This bug fix skips the load balancer resource deletion when no Octavia endpoint is found. Now all OpenStack resources linked to the cluster are removed. (BZ#1725127)
• Previously, OLM failed to generate an upgraded CSV with a `Spec.Replaces` field when the following Operator conditions were met:
• The Operator being upgraded provided a required API whose GVK had not changed since the previous version of the Operator.
• The Operator used the `skipRange` field instead of the `Spec.Replaces` field.

The failed CSV upgrade is outlined by the following OLM sequence:

1. Add the new Operator to the generation, and mark the APIs it provides as `present`.
2. Remove the old Operator from the generation, and mark the APIs it provides as `absent`, despite being provided by the new version of the Operator.
3. Attempt to resolve the missing APIs, overwriting the new version of the Operator with a copy that does not have its `Spec.Replaces` field set.

The sequence resulted in Operators failing to upgrade to new versions. The OLM has been updated to remove the old Operator from the current generation before adding the new Operator to the new generation. The upgrade now succeeds.
(BZ#1836447)

• Previously, the garbage collection resource event queue was not configured correctly. This caused cluster-scoped resources generated for Operators managed by OLM to never be cleaned up when the Operator was uninstalled. This bug fix reconfigures the garbage collection queues with owner labels referencing any namespace to be assessed. Now cluster-scoped resources generated for Operators managed by OLM are cleaned up when the Operator is uninstalled. (BZ#1841859)
• The Cluster Version Operator (CVO) had a race condition where it would consider a timed-out update reconciliation cycle a successful update. This only happened for restricted network clusters where the Operator timed out attempting to fetch release image signatures. This bug caused the CVO to enter its shuffled-manifest reconciliation mode, which could break the cluster if the manifests were applied in an order that the components could not handle. The CVO now treats timed-out updates as failures, so it no longer enters reconciling mode before the update succeeds. (BZ#1846177)

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

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

The image digest is sha256:449b9b839d2cdf33ff2a494a5863d24dc1b436f995c286d8f8d58821ae293b82

(For s390x architecture)

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

The image digest is sha256:2750133b6ca270ebe340da28cb6c6923e6eb23935435063ae2a3a9a8ad6c3819

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

Solution

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

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

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

Affected Products

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

Fixes

• BZ - 1725127 - [IPI] [OSP] Destroy cluster fails because it cannot find an endpoint
• BZ - 1772743 - ASB/TSB operators failed to upgrade on 4.2.z for no "olm.skipRange" or "replace" field in CSVs
• BZ - 1805427 - Unable to deploy NFD from github on release-4.2 branch
• BZ - 1808549 - [4.2] duplicate delete commands are seen when deleting PVs backed by vsphere volumes; first call succeeds, second fails with disk not found
• BZ - 1810136 - [4.2] A pod that gradually leaks memory causes node to become unreachable for 10 minutes
• BZ - 1825372 - e2e: Failing test - Pod Container Status should never report success for a pending container
• BZ - 1828341 - [4.2] RHEL 7.8: cleaning up mounts of Kubernetes service account secrets of deleted pods failing
• BZ - 1836447 - Operator update is failing due to missing replace field in Operator CSV
• BZ - 1840461 - Applying "ctrcfg" causes cri-o to fail to upgrade a cluster
• BZ - 1840763 - [4.2] openshift-sdn does not update egress IPs on the node due to deadlock
• BZ - 1841859 - failed: couldn't find queue operatorname for event: {update }
• BZ - 1842577 - libvirt: add yq to the libvirt ci image
• BZ - 1843767 - OCS 4.3 Installation fails when using OCS 4.4-rc2 registry bundle
• BZ - 1846177 - Unable to upgrade OCP4.3.19 to OCP4.4 in disconnected env: CVO enters reconciling mode without applying any manifests in update mode

CVEs

• CVE-2017-18077
• CVE-2017-18869
• CVE-2018-3737
• CVE-2018-3750
• CVE-2019-16775
• CVE-2019-16776
• CVE-2019-16777
• CVE-2020-8616
• CVE-2020-8617
• CVE-2020-10722
• CVE-2020-10723
• CVE-2020-10724
• CVE-2020-10749
• CVE-2020-10772
• CVE-2020-11008
• CVE-2020-11619
• CVE-2020-11620
• CVE-2020-13777

References

(none)