Red Hat Product Errata RHBA-2020:4198 - Bug Fix Advisory
Issued:
2020-10-27
Updated:
2020-10-27

RHBA-2020:4198 - Bug Fix Advisory

Synopsis

OpenShift Container Platform 4.6.1 extras update

Type/Severity

Bug Fix Advisory

Topic

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

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

All OpenShift Container Platform 4.6 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 https://docs.openshift.com/container-platform/4.6/updating/updating-cluster-between-minor.html#understanding-upgrade-channels_updating-cluster-between-minor.

Solution

For OpenShift Container Platform 4.6 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.6/release_notes/ocp-4-6-release-notes.html

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

Affected Products

  • Red Hat OpenShift Container Platform 4.6 for RHEL 8 x86_64
  • Red Hat OpenShift Container Platform 4.6 for RHEL 7 x86_64
  • Red Hat OpenShift Container Platform for Power 4.6 for RHEL 8 ppc64le
  • Red Hat OpenShift Container Platform for IBM Z and LinuxONE 4.6 for RHEL 8 s390x

Fixes

  • BZ - 1671226 - Execute es_load_kibana_ui_objects in ES pod failed.
  • BZ - 1801472 - OCP 4.2.18 Stage - Update Channel for NFD Operator needs to default to ver 4.2 when deploying operator from OperatorHub
  • BZ - 1828907 - The elasticsearch deployments weren't updated
  • BZ - 1834411 - Placeholder bug for OCP 4.6.0 extras release
  • BZ - 1849564 - The status of Kibana pod is always notReady in the Kibana CR.
  • BZ - 1852341 - 2020-06-03 08:34:06 +0000 [warn]: got unrecoverable error in primary and no secondary error_class=ArgumentError error="'Metadata' is not a designated severity"
  • BZ - 1861961 - Could't use IPv6 Address as URL in ClusterLogForwarder
  • BZ - 1862050 - Connection refused on fluentd metrics on IPv6 single stack cluster
  • BZ - 1862367 - Couldn't gather the infra logs when enabled both ns filter inputref and infrastructure
  • BZ - 1864397 - SSLError in fluentd logs when deploying CLO 4.6
  • BZ - 1865364 - Elasticsearch operator does not alert for out of file descriptors
  • BZ - 1865777 - [IBM Power]Elasticsearch pods are not ready
  • BZ - 1866019 - elasticsearch-rollover and elasticsearch-delete pods in Error states
  • BZ - 1866020 - Operator alerts for error count and should alert for error rate
  • BZ - 1866531 - LOG-802 forwarder: infrastructure logs are sent to application pipelines.
  • BZ - 1866537 - Fix collector config which says it is not used
  • BZ - 1866681 - Cluster Log Forwarder: the labels added in pipelines are not added to the log messages.
  • BZ - 1867129 - Collector tuning: No default values are set in fluent.conf for forwarder.fluentd.buffer
  • BZ - 1867461 - Kibana error when trying to view logs - "Error: [security_exception] no permissions for [indices:data/read/field_stats]"
  • BZ - 1867687 - Changed location of some audit logs in 4.6
  • BZ - 1867759 - Node Infra logs are not collected
  • BZ - 1868068 - The fluentd-init container image wasn't updated
  • BZ - 1868280 - Found `Could not create ServiceMonitor object` when EO/CLO start.
  • BZ - 1868282 - Should get some error message when creating clusterlogging with 1 es node and SingleRedundancy.
  • BZ - 1868300 - ElasticSearch operator upgrade created new PVCs
  • BZ - 1868416 - Elasticsearch image provides 6.8.1-SNAPSHOT version
  • BZ - 1868616 - [RFE] enable NFD operator to deploy nfd-worker pods on nodes labeled other than "node-role.kubernetes.io/worker"
  • BZ - 1869117 - Infra/app/audit indices couldn't be created in default ES due to `Failed to reconcile PrometheusRules for Elasticsearch cluster: failed to build prometheus rule.`
  • BZ - 1870289 - Put ClusterLogForwarer into cluster scope
  • BZ - 1870650 - CPaaS RHEL8: Fluentd supervisor.rb:777:in `initialize': No such file or directory
  • BZ - 1870653 - CPaaS RHEL8: python3 print Compatibility error in ose-logging-elasticsearch6
  • BZ - 1870898 - User "system:serviceaccount:openshift-logging:cluster-logging-operator" cannot list resource "clusterloggings" in API group "logging.openshift.io" at the cluster scope
  • BZ - 1871210 - The metering and reporting operator are missing the `summary` label which fails the inherited_labels CVP check
  • BZ - 1871224 - Metering is using the wrong downstream logo
  • BZ - 1871274 - Elasticsearch operator should have consistent and helpful log messages
  • BZ - 1871721 - Add missing CRD category for cluster-logging-operator provided CRDs
  • BZ - 1871737 - Update CRD apiVersion to apiextensions.k8s.io/v1
  • BZ - 1872425 - Missing namespaces in cpu report and memory report
  • BZ - 1873013 - Alert `ElasticsearchNodeDiskWatermarkReached` couldn't become Pending/Firing.
  • BZ - 1873396 - [cluster-logging-operator] Make lint target mandatory for CI builds
  • BZ - 1873493 - ElasticsearchSecurityException-after upgrade of OCP 4.5.4 to 4.5.6
  • BZ - 1873611 - Fluentd configmap is no longer a pretty editable string
  • BZ - 1873652 - Upgrade from 4.4 to 4.5: Failed to reconcile Elasticsearch deployment spec: Could not create node resource: Deployment.apps is invalid
  • BZ - 1874081 - Fix 4.4->4.5 upgrade test
  • BZ - 1874652 - The MeteringConfig CRD is missing the db.secretName property
  • BZ - 1874746 - The `status` field in the clusterlogging/instance is empty
  • BZ - 1875461 - Cluster Logging Operator CSV should provide drop down for storageClassName selection
  • BZ - 1875478 - Rename "Monitoring" to "Observability" for the external console links group
  • BZ - 1876236 - The label [tuned.openshift.io/elasticsearch: "true"] is still present in the ElasticSearch Deployment
  • BZ - 1878123 - Action required: Update the cluster-logging-operator and elasticsearch-operator to client-go v1.18.8
  • BZ - 1878305 - Error 504: Internal Server Error on Kibana
  • BZ - 1879328 - ES pod stuck in `CrashLoopBackOff` due to `Could not create the Java Virtual Machine.`
  • BZ - 1879748 - elasticsearch-proxy hides 401 auth response from api server by always returning 500
  • BZ - 1880012 - Move custom Ginkgo matchers to matchers package.
  • BZ - 1880845 - After upgrade from OCP v4.3.29 to v4.4.10 cluster-logging-operator is in CrashLoopBackOff
  • BZ - 1880926 - The EO can't recreate ES deployments after upgrade cluster from 4.5 to 4.6
  • BZ - 1881748 - Should use OCP rather than OKD
  • BZ - 1882232 - Couldn't get ES indices with cluster-admin user's token
  • BZ - 1882525 - elasticsearch-delete KeyError: 'is_write_index'
  • BZ - 1883079 - undefined local variable or method `use_nil' when logfoward to kafka using secret
  • BZ - 1883674 - wrong image on master branch manifests
  • BZ - 1884275 - Put the ClusterLogForwarder back into namespace scope

References

(none)

The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.