RHBA-2023:0386 - Bug Fix Advisory

Topic

Logging Subsystem 5.5.6 - Red Hat OpenShift

Description

Logging Subsystem 5.5.6 - Red Hat OpenShift

Solution

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

For details on how to apply this update, refer to:

https://access.redhat.com/articles/11258

Affected Products

• Logging Subsystem for Red Hat OpenShift for ARM 64 5 for RHEL 8 aarch64
• Logging Subsystem for Red Hat OpenShift 5 for RHEL 8 x86_64
• Logging Subsystem for Red Hat OpenShift for IBM Power, little endian 5 for RHEL 8 ppc64le
• Logging Subsystem for Red Hat OpenShift for IBM Z and LinuxONE 5 for RHEL 8 s390x

Fixes

• LOG-3340 - [release-5.5] Collector pod violates PodSecurity "restricted:v1.24" when using lokistack as the default log store in OCP 4.12.
• LOG-3407 - [release-5.5] Cluster logging pod multiple times crashed when some capabilities is disabled.
• LOG-3428 - v5.5.6-8 cluster-logging-operator pod ends up in CrashLoopBackOff status
• LOG-3341 - ElasticsearchError error="400 - Rejected by Elasticsearch" when adding some labels in application namespaces
• LOG-3469 - [release-5.5] CLF raises 'invalid: unrecognized outputs: [default]' after adding `default` to outputRefs.
• LOG-3342 - [release-5.5]OutputDefaults is being applied to any ES output rather than only default
• LOG-3472 - [must-gather] oc adm must-gather execution hangs indefinitely when collecting information for Cluster Logging.
• LOG-3511 - [release-5.5] TLS errors on Loki controller pod due to bad certificate

CVEs

• CVE-2021-46848
• CVE-2022-2056
• CVE-2022-2057
• CVE-2022-2058
• CVE-2022-2519
• CVE-2022-2520
• CVE-2022-2521
• CVE-2022-2867
• CVE-2022-2868
• CVE-2022-2869
• CVE-2022-2953
• CVE-2022-2964
• CVE-2022-4139
• CVE-2022-35737
• CVE-2022-42010
• CVE-2022-42011
• CVE-2022-42012
• CVE-2022-42898
• CVE-2022-43680

References

• null