Topic

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

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

This update fixes the following bugs among others:

• During container image deployment, if an internal image was selected as a

Knative service, a duplicate imagestream was created for the image. Because
there were duplicate imagestreams, the image deployment would fail. The issue with creating a duplicate imagestream is fixed, allowing internal images to successfully deploy as a Knative service.(BZ#1808282)

• The secondary masthead in the web console's Developer perspective was no

longer sticky. The styles have been modified and the masthead now properly
displays. (BZ#1808436)

• Service binding requests (SBR) were associated with revisions in the topology view. Because of this, revisions were unable to get associated secrets. SBRs are now created with the Knative service, allowing secrets to be injected for newly created revisions. (BZ#1808968)

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.3/release_notes/ocp-4-3-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.3.8-x86_64

The image digest is sha256:a414f6308db72f88e9d2e95018f0cc4db71c6b12b2ec0f44587488f0a16efc42

All OpenShift Container Platform 4.3 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.3 see the following documentation, which
will be updated shortly for release 4.3.8, for important instructions on
how to upgrade your cluster and fully apply this asynchronous errata
update:

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

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

Affected Products

• Red Hat OpenShift Container Platform 4.3 for RHEL 8 x86_64
• Red Hat OpenShift Container Platform 4.3 for RHEL 7 x86_64

Fixes

• BZ - 1777301 - No option to select bucket class in Object bucket claim creation
• BZ - 1781833 - [IPI Baremetal]: baremetal-operator should support virtual media
• BZ - 1785279 - Machine config pool reports Degraded when audit is enabled
• BZ - 1791022 - 4.3 operator should remove 4.4-only resources on downgrade from 4.4
• BZ - 1792309 - [4.3] ovn-kubernetes ipv6 support for cluster-network-operator
• BZ - 1792847 - Failed / cancelled migration shows incorrect status and node in the UI
• BZ - 1793635 - Workloads on GCP are unreachable during 4.2.x to 4.3.0 upgrade sometimes
• BZ - 1794009 - Incorrect memory loads from edited vm template
• BZ - 1794176 - Summary for 'Operator Registry ' containers is wrong
• BZ - 1795302 - oc: error: No Auth Provider found for name "gcp"
• BZ - 1795617 - UsingDeprecatedAPIExtensionsV1Beta1 alert does not clear
• BZ - 1795665 - Nightly upgrade tuned pods couldn't be started
• BZ - 1796186 - Enable pipelines for Knative and Kubernetes apps on import
• BZ - 1796675 - `oc adm catalog build` should immediately error out if it can't find any data in appregistry
• BZ - 1797019 - ClusterServiceVersion resource with Deleting status is never removed
• BZ - 1797042 - [4.3] [egressIP] The iptables related to stale egress ip was not removed.
• BZ - 1798142 - EgressNetworkPolicy OpenAPI spec missing properties
• BZ - 1798665 - Catalog Operator pod hangs indefinitely if it can't reach the api server when starting
• BZ - 1799540 - Gathering virt platform info is not complete due to insufficient privileges for some bios detection
• BZ - 1800315 - Machine controller must wait for node to be fully terminated before deleting Kube Node object
• BZ - 1800809 - Could not forward logs to rsyslog server
• BZ - 1801261 - ROKS: cloud credential operator is not getting excluded by CVO [4.3]
• BZ - 1801367 - Typo on test-e2e make target
• BZ - 1801384 - [4.3]Bump to OVN2.12
• BZ - 1801417 - [4.3]Bump ovnkube to support OVN2.12
• BZ - 1801446 - AWS: Remove installer IAM permissions pre-check for UPI deployments
• BZ - 1801737 - [4.3] kube-proxy periodic iptables reloads are extremely disruptive in large clusters
• BZ - 1801801 - Document how to refresh certificates on day 2
• BZ - 1803080 - openshift-apiserver 4.3: Unbounded valuesets for metric labels
• BZ - 1803122 - [4.3] cannot interact with toolbox container after first execution
• BZ - 1803135 - Unable to Re-install kubevirt-hyperconverged Operator
• BZ - 1804078 - [OVN][4.3.z backport]On azure/AWS env when restart master node met error: reason:NetworkPluginNotReady message:Network plugin returns error: Missing CNI default network
• BZ - 1804494 - docker-registry image has ~50M of extra content due to yum cache
• BZ - 1805116 - Prometheus federation write is failing on a large scale cluster
• BZ - 1805268 - The configmap sourceType of the CatalogSource failed to connect the ConfigMap
• BZ - 1805317 - Telemeter payload limit is too small for larger clusters
• BZ - 1805388 - [4.3.z] improve reliability during upgrade by using a deployment
• BZ - 1805815 - [Disconnected] openshift-samples operator setting management state to Removed does not complete while Progressing==true
• BZ - 1807037 - Cluster does not work any longer after a failed cluster with the same name is destroyed
• BZ - 1807062 - route-override CNI and whereabouts IPAM CNI should be installed in OpenShift
• BZ - 1807104 - Running the OLM and OperatorHub configuration for restricted networks in an IPv6 bare metal deployment leaves nodes in NotReady,SchedulingDisabled state
• BZ - 1807203 - Disconnected Installation of 4.3.x fails when using a self signed certificate and additionalTrustBundle in install-config.yaml
• BZ - 1807279 - Large number of etcd leader elections on Azure
• BZ - 1807291 - Wrong sort criteria for capacity on console
• BZ - 1807775 - Not every pod in the vanilla openshift installation set cpu resource request
• BZ - 1807812 - oc image mirror --from-dir does not override --dir
• BZ - 1808095 - Installer panic when selecting from an empty options list
• BZ - 1808282 - Deploy Image: "Image name from internal registry" with Knative Service creates a broken ImageStream
• BZ - 1808419 - If OLM catalog operator cannot reach the API server, it does not seem to retry
• BZ - 1808436 - The project selector should always be "sticky" - [openshift 4.3]
• BZ - 1808482 - No way for users to specify custom OS image location
• BZ - 1808602 - kube-apiserver operator should go upgradeable=false if SCC has changed
• BZ - 1808968 - Service binding should be through Knative Service
• BZ - 1809253 - [4.3.z] 502 error for Prometheus API after the cluster running overnight
• BZ - 1809283 - [4.3] Multus should not cause machine to go not ready when Multus is updated
• BZ - 1809360 - The `--from` info should point to the `operator-registry` image from the release stream
• BZ - 1809532 - openshift-apiserver operator not available when used for single node cluster (CRC)
• BZ - 1809649 - subscription_sync_count metric should contain package name
• BZ - 1809693 - MachineConfigDaemonReasonAnnotationKey gives node description beyond 262144 characters
• BZ - 1809866 - Failed to mirror image to intergrated registry with "manifest invalid" error sometimes
• BZ - 1810018 - [IPI] [OSP] openshift-install got failed for floatingip creation if rhcos base image uploading take more than 10m0s
• BZ - 1810048 - OperatorSource failed on IPv6 cluster since Quay doesn't support IPv6
• BZ - 1810306 - [4.3] No controller metrics reported from 4.3 openshift-controller-manager
• BZ - 1810420 - [4.3] "You are attempting to import a cert with the same issuer/serial as an existing cert, but that is not the same cert" on FIPS enabled cluster after upgrade
• BZ - 1810533 - oc image mirror shouldn't default to mirroring manifest lists
• BZ - 1810596 - 4.4: 4.3 openshift-apiserver-operator should go upgradeable=false if SCC has changed – noop
• BZ - 1810959 - `oc adm inspect namespace` doesn't collect pod logs
• BZ - 1811154 - [4.3] GCP UPI cluster cluster name regex check does not support '.' in cluster name
• BZ - 1811525 - Save button on Pipelines Resources tab is not enabled even if all required fields are filled.[release-4.3]
• BZ - 1812599 - ip=dhcp,dhcp6 kernel command line doesn't work for ipv4 deployments

CVEs

• CVE-2020-10531

References

(none)