RHBA-2018:3537 - Bug Fix Advisory

Topic

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

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

https://access.redhat.com/errata/RHBA-2018:3536

Space precludes documenting all of the bug fixes and enhancements 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/3.11/release_notes/ocp_3_11_release_notes.html

All OpenShift Container Platform 3.11 users are advised to upgrade to these updated packages.

Solution

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

See the following documentation, which will be updated shortly for release 3.11.43, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update:

https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_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.11 x86_64

Fixes

• BZ - 1552304 - CRI-O pod log lines are occasionally split mid-line
• BZ - 1613722 - Eventrouter creates duplicated events every 30 min with verb UPDATE
• BZ - 1614904 - Validation of static pod fails due to inconsistent names
• BZ - 1615884 - Ability to install a cluster with a mix of Docker and CRI-O nodes
• BZ - 1622822 - Logging should restricted to to current owner/group of a namespace.
• BZ - 1625090 - [CNS][3.11] Run standalone deployment playbook with glusterfs_registry group failed due to AnsibleUndefinedVariable
• BZ - 1626228 - Sometimes builds on api.ci fail with "no such image"
• BZ - 1626538 - openshift-ansible in 3.11 fails OCP 3.11 on OSP 13
• BZ - 1627086 - ElasticSearch pods flapping with "fatal error on the network layer" exception when logging from 1000+ nodes
• BZ - 1627689 - The elasticsearch-config should be logging-elasticsearch-ops in logging-es-ops pods
• BZ - 1628235 - Service Catalog establishes a new connection for every request and never closes them.
• BZ - 1628381 - [docs] Document expectations regarding operational management of NodeWithImpairedVolumes
• BZ - 1628902 - Meet 'openshift_is_atomic' is undefined during execute CNS standalone deployment playbook with glusterfs_registry group
• BZ - 1629558 - Fail to atomic pull node image due to docker service was stopped in previous task
• BZ - 1632364 - [3.11] Fluentd cannot handle S2I Logs
• BZ - 1632648 - [3.11] Record is missing kubernetes field when use '--log-driver journald' in /etc/sysconfig/docker
• BZ - 1632895 - [3.11] logging-eventrouter event not formatted correctly in Elasticsearch when using MUX
• BZ - 1633574 - Should not assign the egressIP to node automatically if there are multiple egressIPs in the project
• BZ - 1633923 - openshift-autoheal fails to install in disconnected install
• BZ - 1634700 - [3.11] Modification in master-config.yaml is causing a failure during Master-API restart (runtime-config)
• BZ - 1634835 - Glusterfs-registry pods also get removed while only glusterfs is being uninstalled
• BZ - 1635672 - Use GLUSTER_BLOCKD_STATUS_PROBE_ENABLE enabled templates in glusterfs playbooks
• BZ - 1636248 - not enough master nodes discoverd because service logging-es-cluster is not headless
• BZ - 1637413 - 3.11: APP pod unable to start after target port failure in cases where single paths are mounted on APP pods(BZ#1599742)
• BZ - 1637737 - Service catalog controller segmentation fault
• BZ - 1641245 - Upgrade to 3.11 on atomic host fails during Install or Update node system container task
• BZ - 1641321 - Pods in error state after installing OpenShift with OSP14
• BZ - 1641657 - [3.11] Registry doesn't honors openshift_additional_ca
• BZ - 1641796 - controller-manager pod stops responding with max memory usage and lot of open tcp sockets
• BZ - 1642002 - cockpit-docker is installed (and docker as dependency) even if you just want to use cri-o
• BZ - 1642350 - Failure to restore cache produces corrupted files passed to incremental builds
• BZ - 1643119 - Secure ldap identity provider fails to query the LDAP server. "tls: bad record MAC"
• BZ - 1643301 - Provisioning two APB services temporarily broke networking in the namespace
• BZ - 1643948 - Cluster console doesn't display the real value of Crashlooping Pods (it displays 0)

CVEs

(none)

References

(none)