Synopsis

OpenShift Container Platform 3.5, 3.4, and 3.3 bug fix update

Type/Severity

Bug Fix Advisory

Topic

Red Hat OpenShift Container Platform releases 3.5.5.31, 3.4.1.44, and 3.3.1.36 are now available with updates to packages and images that fix several bugs.

Description

Red Hat OpenShift Container Platform is the company's cloud computing Platform-as-a-Service (PaaS) solution designed for on-premise or private cloud deployments.

This advisory contains the RPM packages for Red Hat OpenShift Container Platform 3.5.5.31, 3.4.1.44, and 3.3.1.46. See the following advisory for the container images for this release:

https://access.redhat.com/errata/RHBA-2017:1829

This update fixes the following bugs:

• A bug in a regulator of concurrent file system access could cause a routine to hang. When the registry configured with the file system storage driver had been under heavy load, some could hang indefinitely. With this bug fix, the issue with the regulator is addressed and the concurrent pushes no longer hang. (BZ#1465325)
• Sometimes during index recovery, the SG ACL initialization would fail because the cluster did not get into the proper state before timing out. The ES cluster is rendered unusable because there is no initial authorization and no requests are allowed. Continually try to seed the SG ACLs until they succeed and the ES is functional. (BZ#1470368)
• Use underscores instead of dashes for the memory switch. Memory settings are now respected by the nodejs runtime. (BZ#1468734, BZ#1468987)
• The storage path needed to be evaluated correctly for ops clusters. Use the information from the logging facts to determine if a volume should be reused. (BZ#1466695)
• The installer handles both installation and configuration of logging during the initial deployment, as well as post-deployment by calling one of the ad-hoc playbooks. In the case where a default project nodeselector was used for the initial installation, the ad-hoc logging deployment would fail due to selector conflicts. Now, the logging project is force created with a null nodeselector to avoid conflicts regardless of when the logging deployment is performed. (BZ#1470394)
• The JSON fields validation for the List element on the "From File" page was wrong. List could not be created due to its missing metadata field. Validation will now check if the element that is being created is a List and, if so, will skip metadata validation. The List element can now be created on the "From File" page. (BZ#1407186)

All OpenShift Container Platform 3.5, 3.4, and 3.3 users are advised to upgrade to these updated packages and images.

Solution

Before applying this update, make sure all previously released errata relevant to your system have been applied.

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

https://docs.openshift.com/container-platform/3.5/release_notes/ocp_3_5_release_notes.html

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

https://docs.openshift.com/container-platform/3.4/release_notes/ocp_3_4_release_notes.html

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

https://docs.openshift.com/container-platform/3.3/release_notes/ocp_3_3_release_notes.html

This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/articles/11258.

Affected Products

• Red Hat OpenShift Container Platform 3.5 x86_64
• Red Hat OpenShift Container Platform 3.4 x86_64
• Red Hat OpenShift Container Platform 3.3 x86_64

Fixes

• BZ - 1407186 - Some resources defined in List couldn't be created through Import YAML/JSON
• BZ - 1408676 - [3.3+][Registry][Pruning] Orphaned blobs cannot be pruned
• BZ - 1460271 - [3.5] High CPU Utilization Openshift process
• BZ - 1461635 - [3.3] Hawkular Metrics cannot handle connecting to the Kubernetes Master when the ca.crt contains multiple certificates.
• BZ - 1465325 - [3.5][Backport] Concurrent build registry push hangs - baremetal cluster with CNS Gluster registry storage
• BZ - 1466695 - Running the logging playbooks resets elasticsearch-storage volume for es-ops
• BZ - 1467708 - [3.4] Don't rely on device name provided by Cinder
• BZ - 1467970 - Timeouts with Azure Disk attaching volumes to pods
• BZ - 1468308 - [3.5] Hawkular Metrics cannot handle connecting to the Kubernetes Master when the ca.crt contains multiple certificates.
• BZ - 1468734 - Kibana-proxy gets OOMKilled
• BZ - 1468987 - [3.4] Kibana-proxy gets OOMKilled
• BZ - 1470368 - SearchGuard times out seeding ES pod's .seachguard.$HOSTNAME index
• BZ - 1470394 - Logging playbook run in isolation ignores/conflicts with default node selector
• BZ - 1471844 - [3.4][Registry][Pruning] Orphaned blobs cannot be pruned
• BZ - 1472438 - [3.5][Registry][Pruning] Orphaned blobs cannot be pruned
• BZ - 1473599 - KIBANA_MEMORY_LIMIT: unbound variable
• BZ - 1474431 - controller-manager panic/crash on volume verification

CVEs

(none)

References

(none)