- Issued:
- 2019-08-28
- Updated:
- 2019-08-28
RHBA-2019:2547 - Bug Fix Advisory
Synopsis
OpenShift Container Platform 4.1.13 bug fix update
Type/Severity
Bug Fix Advisory
Topic
Red Hat OpenShift Container Platform release 4.1.13 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.1.13. See the following advisory for the
RPM packages for this release:
https://access.redhat.com/errata/RHBA-2019:2546
This release fixes the following bugs:
- Kibana would present a blank page or time out errors due to too many calls to the ElasticSearch cluster. Now, caching of the API calls and dynamic seeding allows for more efficiency and reduces the opportunity for page timeouts. (BZ#1726434)
- The drain process would not terminate the image registry pod properly. The registry process has been amended so that it now receives SIGTERM and properly evicts the image registry during the drain process. (BZ#1737379)
- Openvswitch (OVS) was missing from the SDN as a result of an internal build issue. This has been resolved with this release. (BZ#1740264)
- The default minimum install of Red Hat Enterprise Linux included firewalld.service, which blocks ports by default. Now, firewalld is disabled if installed. (BZ#1740964)
- The samples operator was not setting the reason or message information it generated for various errors it detected on it's ClusterOperator object's Degraded condition. As a result, Useful diagnostic information on the samples operator was not readily available from the telemetry console. Now, the message information is not set on the ClusterOperator object's Degraded condition. Useful diagnostic information on the samples operator is now available from the telemetry console. (BZ#1742907)
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.1/release_notes/ocp-4-1-rel ease-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.1.13
The image digest is sha256:212296a41e04176c308bfe169e7c6e05d77b76f403361664c3ce55cd30682a94
All OpenShift Container Platform 4.1 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.1 see the following documentation, which
will be updated shortly for release 4.1.13, for important instructions on
how to upgrade your cluster and fully apply this asynchronous errata
update:
https://docs.openshift.com/container-platform/4.1/release_notes/ocp-4-1-release-notes.html
Details on how to access this content are available at
https://docs.openshift.com/container-platform/4.1/updating/updating-cluster-cli.html.
Affected Products
- Red Hat OpenShift Container Platform 4.1 for RHEL 7 x86_64
Fixes
- BZ - 1696737 - upgrade dialog not expanding to show versions dropdown
- BZ - 1707827 - cloud-credential-operator did not upgrade
- BZ - 1711044 - The ES deployment couldn't be created if the origin one is deleted in stuck
- BZ - 1712955 - Can't scale up ES nodes from 3 to N (N>3) in clusterlogging CRD instance.
- BZ - 1714168 - [4.1] Cannot change Requests values in image-registry operator config
- BZ - 1723851 - Operators requesting cluster-scoped permission can trigger kube GC bug
- BZ - 1725249 - Elasticsearch Operator sets resource limits when not requested
- BZ - 1726144 - [backport 4.1] must-gather gather_network_logs script does not save output under /must-gather
- BZ - 1726434 - kibana presenting blank page or timeout
- BZ - 1726866 - invalid machine config should cause a RenderDegraded error not NodeDegraded
- BZ - 1728105 - oc adm node-logs --since today option doesn't work
- BZ - 1731855 - Add SearchGuard permissions for Jaeger to create index templates.
- BZ - 1732166 - `/etc/kubernetes/ca.crt` is not managed/updated [backport to 4.1.z]
- BZ - 1732214 - catalog-operator panic on labelling ClusterRole/ClusterRoleBinding
- BZ - 1732588 - [marketplace] certified-operators causing e2e failures
- BZ - 1732934 - `oc explain apiserver.spec.servingCerts` still explains defaultServingCertificate
- BZ - 1733232 - Cert validity increases from 1 year to 10 years during rotation
- BZ - 1733978 - [4.1] oauth-openshift operand not starting
- BZ - 1734083 - Add Jaeger index mappings to Elasticsearch image
- BZ - 1734663 - [4.1] Backport of upstream #78882: Fix incorrect procMount defaulting
- BZ - 1735709 - Build Defaults not being applied to pods
- BZ - 1737379 - [4.1] drain takes 600s to evict the image-registry pod and container is still running afterwards
- BZ - 1739085 - Multi-version CRDs and admission webhooks do not play nicely together in OpenShift 4.1
- BZ - 1739218 - Placeholder for 4.1.11 RPM release
- BZ - 1739219 - [4.1.z] Image Registry's service CA is constantly removed/re-created
- BZ - 1739322 - The tuned pod doesn't set max virtual memory areas vm.max_map_count for elasticsearch pod in node.
- BZ - 1740174 - The generated InstallPlan object didn't refer to itself subscription object
- BZ - 1740264 - SDN is missing OVS installed
- BZ - 1740373 - Cluster infrastructure CPU/memory accounting doesn't cover nodes, system level processes
- BZ - 1740391 - Enable running make verify as a CI job
- BZ - 1740824 - Marketplace operator enters degraded & ultimately exits during upgrade
- BZ - 1740964 - [Backport 4.1]Unless RHEL worker disable firewalld.service, "oc rsh/exec/logs" does not work
- BZ - 1741039 - [4.1] Storage-admin can get but not describe pvc from other's project
- BZ - 1741350 - Failed to upgrade ES pods because cpu limit is set to zero in the deployment
- BZ - 1741661 - Telemetry should include the ClusterVersion conditions with reasons
- BZ - 1741753 - cluster-logging-operator image size is too small 52.4 kB
- BZ - 1741959 - errors on events tab of node page
- BZ - 1742907 - samples operator clusteroperator degraded reporting missing reason/detail information
- BZ - 1743293 - kubelet exited with "failed to write xxx to cgroup.procs .. .scope/cgroup.procs: invalid argument [4.1]
CVEs
- CVE-2016-3186
- CVE-2016-3616
- CVE-2016-10166
- CVE-2016-10713
- CVE-2016-10739
- CVE-2017-9118
- CVE-2017-9120
- CVE-2017-12932
- CVE-2017-14503
- CVE-2017-16642
- CVE-2018-0495
- CVE-2018-0734
- CVE-2018-1122
- CVE-2018-3058
- CVE-2018-3063
- CVE-2018-3066
- CVE-2018-3081
- CVE-2018-3282
- CVE-2018-5711
- CVE-2018-5712
- CVE-2018-5741
- CVE-2018-6952
- CVE-2018-7456
- CVE-2018-7584
- CVE-2018-7755
- CVE-2018-8087
- CVE-2018-8905
- CVE-2018-9363
- CVE-2018-9516
- CVE-2018-9517
- CVE-2018-10545
- CVE-2018-10546
- CVE-2018-10547
- CVE-2018-10548
- CVE-2018-10549
- CVE-2018-10779
- CVE-2018-10853
- CVE-2018-10963
- CVE-2018-11212
- CVE-2018-11213
- CVE-2018-11214
- CVE-2018-11813
- CVE-2018-12404
- CVE-2018-12641
- CVE-2018-12697
- CVE-2018-12900
- CVE-2018-13053
- CVE-2018-13093
- CVE-2018-13094
- CVE-2018-13095
- CVE-2018-14348
- CVE-2018-14498
- CVE-2018-14598
- CVE-2018-14599
- CVE-2018-14600
- CVE-2018-14625
- CVE-2018-14647
- CVE-2018-14734
- CVE-2018-14851
- CVE-2018-14884
- CVE-2018-15473
- CVE-2018-15594
- CVE-2018-15853
- CVE-2018-15854
- CVE-2018-15855
- CVE-2018-15856
- CVE-2018-15857
- CVE-2018-15859
- CVE-2018-15861
- CVE-2018-15862
- CVE-2018-15863
- CVE-2018-15864
- CVE-2018-16062
- CVE-2018-16402
- CVE-2018-16403
- CVE-2018-16658
- CVE-2018-16842
- CVE-2018-16885
- CVE-2018-17082
- CVE-2018-17100
- CVE-2018-17101
- CVE-2018-18074
- CVE-2018-18281
- CVE-2018-18310
- CVE-2018-18384
- CVE-2018-18520
- CVE-2018-18521
- CVE-2018-18557
- CVE-2018-18661
- CVE-2018-20783
- CVE-2018-1000169
- CVE-2018-1000876
- CVE-2018-1000877
- CVE-2018-1000878
- CVE-2019-1559
- CVE-2019-2503
- CVE-2019-2529
- CVE-2019-2614
- CVE-2019-2627
- CVE-2019-2745
- CVE-2019-2762
- CVE-2019-2769
- CVE-2019-2786
- CVE-2019-2816
- CVE-2019-2842
- CVE-2019-3459
- CVE-2019-3460
- CVE-2019-3858
- CVE-2019-3861
- CVE-2019-3882
- CVE-2019-3900
- CVE-2019-5010
- CVE-2019-5489
- CVE-2019-6977
- CVE-2019-7149
- CVE-2019-7150
- CVE-2019-7222
- CVE-2019-7664
- CVE-2019-7665
- CVE-2019-9020
- CVE-2019-9021
- CVE-2019-9022
- CVE-2019-9023
- CVE-2019-9024
- CVE-2019-9637
- CVE-2019-9638
- CVE-2019-9639
- CVE-2019-9640
- CVE-2019-9740
- CVE-2019-9947
- CVE-2019-9948
- CVE-2019-10216
- CVE-2019-10352
- CVE-2019-10353
- CVE-2019-10354
- CVE-2019-11034
- CVE-2019-11035
- CVE-2019-11036
- CVE-2019-11038
- CVE-2019-11039
- CVE-2019-11040
- CVE-2019-11599
- CVE-2019-11810
- CVE-2019-11833
- CVE-2019-1000019
- CVE-2019-1000020
References
(none)
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.