Skip to content

Commit 42437cc

Browse files
committed
OBSDOCS-1546: Logging Z-Stream Release Notes - 6.1.1
1 parent 790e487 commit 42437cc

File tree

2 files changed

+49
-0
lines changed

2 files changed

+49
-0
lines changed

modules/log6x-6-1-1-rn.adoc

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * observability/logging/logging-6.1/log6x-release-notes-6.1.adoc
4+
5+
:_mod-docs-content-type: REFERENCE
6+
[id="logging-release-notes-6-1-1_{context}"]
7+
= Logging 6.1.1 Release Notes
8+
9+
This release includes link:https://access.redhat.com/errata/RHBA-2024:10992[{logging-uc} {for} Bug Fix Release 6.1.1].
10+
11+
[id="logging-release-notes-6-1-1-enhancements_{context}"]
12+
== New Features and Enhancements
13+
14+
* With this update, the {loki-op} supports configuring the workload identity federation on the {gcp-first} by using the Cluster Credential Operator (CCO) in {product-title} 4.17 or later. (link:https://issues.redhat.com/browse/LOG-6420[LOG-6420])
15+
16+
[id="logging-release-notes-6-1-1-bug-fixes_{context}"]
17+
== Bug Fixes
18+
19+
* Before this update, the collector was discarding longer audit log messages with the following error message: *Internal log [Found line that exceeds max_line_bytes; discarding.]*. With this update, the discarding of longer audit messages is avoided by increasing the audit configuration thresholds: The maximum line size, `max_line_bytes`, is `3145728` bytes. The maximum number of bytes read during a read cycle, `max_read_bytes`, is `262144` bytes. (link:https://issues.redhat.com/browse/LOG-6379[LOG-6379])
20+
21+
* Before this update, an input receiver service was repeatedly created and deleted, causing issues with mounting the TLS secrets. With this update, the service is created once and only deleted if it is not defined in the `ClusterLogForwarder` custom resource. (link:https://issues.redhat.com/browse/LOG-6383[LOG-6383])
22+
23+
* Before this update, pipeline validation might have entered an infinite loop if a name was a substring of another name. With this update, stricter name equality checks prevent the infinite loop. (link:https://issues.redhat.com/browse/LOG-6405[LOG-6405])
24+
25+
* Before this update, the collector alerting rules included the summary and message fields. With this update, the collector alerting rules include the summary and description fields. (link:https://issues.redhat.com/browse/LOG-6407[LOG-6407])
26+
27+
* Before this update, setting up the custom audit inputs in the `ClusterLogForwarder` custom resource with configured `LokiStack` output caused errors due to the nil pointer dereference. With this update, the Operator performs the nil checks, preventing such errors. (link:https://issues.redhat.com/browse/LOG-6449[LOG-6449])
28+
29+
* Before this update, the `ValidLokistackOTLPOutputs` condition appeared in the status of the `ClusterLogForwarder` custom resource even when the output type is not `LokiStack`. With this update, the `ValidLokistackOTLPOutputs` condition is removed, and the validation messages for the existing output conditions are corrected. (link:https://issues.redhat.com/browse/LOG-6469[LOG-6469])
30+
31+
* Before this update, the collector did not correctly mount the `/var/log/oauth-server/` path, which prevented the collection of the audit logs. With this update, the volume mount is added, and the audit logs are collected as expected. (link:https://issues.redhat.com/browse/LOG-6484[LOG-6484])
32+
33+
* Before this update, the `must-gather` script of the {clo} might have failed to gather the LokiStack data. With this update, the `must-gather` script is fixed, and the LokiStack data is gathered reliably. (link:https://issues.redhat.com/browse/LOG-6498[LOG-6498])
34+
35+
* Before this update, the collector did not correctly mount the `oauth-apiserver` audit log file. As a result, such audit logs were not collected. With this update, the volume mount is correctly mounted, and the logs are collected as expected. (link:https://issues.redhat.com/browse/LOG-6533[LOG-6533])
36+
37+
[id="logging-release-notes-6-1-1-CVEs_{context}"]
38+
== CVEs
39+
40+
* link:https://access.redhat.com/security/cve/CVE-2019-12900[CVE-2019-12900]
41+
* link:https://access.redhat.com/security/cve/CVE-2024-2511[CVE-2024-2511]
42+
* link:https://access.redhat.com/security/cve/CVE-2024-3596[CVE-2024-3596]
43+
* link:https://access.redhat.com/security/cve/CVE-2024-4603[CVE-2024-4603]
44+
* link:https://access.redhat.com/security/cve/CVE-2024-4741[CVE-2024-4741]
45+
* link:https://access.redhat.com/security/cve/CVE-2024-5535[CVE-2024-5535]
46+
* link:https://access.redhat.com/security/cve/CVE-2024-10963[CVE-2024-10963]
47+
* link:https://access.redhat.com/security/cve/CVE-2024-50602[CVE-2024-50602]

observability/logging/logging-6.1/log6x-release-notes-6.1.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,4 +6,6 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9+
include::modules/log6x-6-1-1-rn.adoc[leveloffset=+1]
10+
911
include::modules/log6x-6-1-0-rn.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)