- Issued:
- 2021-03-16
- Updated:
- 2021-03-16
RHBA-2021:0749 - OpenShift Container Platform 4.7.2 bug fix update
Synopsis
OpenShift Container Platform 4.7.2 bug fix update
Type/Severity
Bug Fix Advisory None
Topic
Red Hat OpenShift Container Platform release 4.7.2 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.2. See the following advisory for the RPM packages for this release:
https://access.redhat.com/errata/RHBA-2020:0746
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, an API server could fail to create a resource, which would return a 409 status code when there was a conflict updating a
resource quotaresource. Consequently, the resource would fail to create, and you might have had to retry the API request. With this update, theOpenShift Consoleweb application attempts to retry the request 3 times when receiving a 409 status code, which is often sufficient for completing the request. In the event that a 409 status code continues to occur, an error will be displayed in the console. (BZ#1928228) -
Previously, the fix for BZ#1871996 to properly create RoleBinding links consistently resulted in the inability to select the binding type when a namespace was selected. Consequently, users with an active namespace could not create a cluster RoleBinding without changing the active namespace to
All namespaces. This update reverts part of the changes for BZ#1871996 so that users can create a cluster role binding regardless of an active namespace. (BZ#1929198) -
Previously, when upgrading a cluster from a prior version with an idled workload, the idled workload would not wake on HTTP request once upgraded to OpenShift Container Platform 4.6/4.7. This error was due to
oc idleupdates and reworks. With this update, idling changes are mirrored from endpoints to services on Ingress Operator startup. As a result, idled routes are now awoken and made accessible withcurl. (BZ#1927080) -
Previously, failing to adopt an externally provisioned host (i.e., hosts from
OpenShift-installer'sdeployment of the control plane) did not automatically retry. Consequently, control plane hosts were often shown inoc bmhasfailed. With this update, failed adoption of the control plane hosts automatically retry to ensure they are always adopted. (BZ#1932452)
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:83fca12e93240b503f88ec192be5ff0d6dfe750f81e8b5ef71af991337d7c584
(For s390x architecture)
$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.6.20-s390x
The image digest is sha256:e32040d23234e21f1b4ecc500533934996708c91587497a17ded2b89b36f72b4
(For ppc64le architecture)
$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.6.20-ppc64le
The image digest is sha256:7ade98079920be8823cf69bae41aa48fb8dac3ce22e01cf5afb0d42237ad83ed
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 This page is not included, but the link has been rewritten to point to the nearest parent document.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 This page is not included, but the link has been rewritten to point to the nearest parent document.https://docs.openshift.com/container-platform/4.7/updating/updating-cluster-cli.html.
Affected Products
| Product | Version | Arch |
|---|---|---|
| Red Hat OpenShift Container Platform | 4.7 | x86_64 |
| Red Hat OpenShift Container Platform for Power | 4.7 | ppc64le |
| Red Hat OpenShift Container Platform for IBM Z and LinuxONE | 4.7 | s390x |
Fixes
- This content is not included.BZ - 1890513
- This content is not included.BZ - 1896170
- This content is not included.BZ - 1923956
- This content is not included.BZ - 1927080
- This content is not included.BZ - 1927407
- This content is not included.BZ - 1927644
- This content is not included.BZ - 1928023
- This content is not included.BZ - 1928228
- This content is not included.BZ - 1929168
- This content is not included.BZ - 1929198
- This content is not included.BZ - 1929777
- This content is not included.BZ - 1931903
- This content is not included.BZ - 1932002
- This content is not included.BZ - 1932151
- This content is not included.BZ - 1932452
- This content is not included.BZ - 1932488
- This content is not included.BZ - 1932968
- This content is not included.BZ - 1934798
- This content is not included.BZ - 1935585
CVEs
References
(none)
Additional information
- The Red Hat security contact is This content is not included.secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.