Skip to content

Commit 686e28e

Browse files
authored
Merge pull request #88378 from jmagak/logging-6.0.4-rn-4.17
OBSDOCS-1651: Logging 6.0.4 release notes
2 parents 8719696 + be23f22 commit 686e28e

File tree

2 files changed

+37
-0
lines changed

2 files changed

+37
-0
lines changed

modules/log6x-rn-6.0.4.adoc

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * observability/logging/logging-6.0/log6x-release-notes.adoc
4+
5+
:_mod-docs-content-type: REFERENCE
6+
[id="logging-release-notes-6-0-4_{context}"]
7+
= Logging 6.0.4
8+
This release includes link:https://access.redhat.com/errata/RHBA-2025:1228[RHBA-2025:1228].
9+
10+
[id="logging-release-notes-6-0-4-enhancements_{context}"]
11+
== New features and enhancements
12+
13+
* This enhancement adds `OTel` semantic stream labels to the `lokiStack` output so that you can query logs by using both `ViaQ` and `OTel` stream labels.
14+
(link:https://issues.redhat.com/browse/LOG-6580[LOG-6580])
15+
16+
[id="logging-release-notes-6-0-4-bug-fixes_{context}"]
17+
== Bug fixes
18+
19+
* Before this update, the Operator used a cached client to fetch the `SecurityContextConstraint` cluster resource, which could result in an error when the cache is invalid. With this update, the Operator now always retrieves data from the API server instead of using the cache.
20+
(link:https://issues.redhat.com/browse/LOG-6130[LOG-6130])
21+
22+
* Before this update, the Vector startup script attempted to delete buffer lock files during startup. With this update, the Vector startup script no longer attempts to delete buffer lock files during startup.
23+
(link:https://issues.redhat.com/browse/LOG-6348[LOG-6348])
24+
25+
* Before this update, a bug in the `must-gather` script for the `cluster-logging-operator` prevented the `LokiStack` from being gathered correctly when it existed. With this update, the `LokiStack` is gathered correctly.
26+
(link:https://issues.redhat.com/browse/LOG-6499[LOG-6499])
27+
28+
* Before this update, the collector metrics dashboard could get removed after an Operator upgrade due to a race condition during the change from the old to the new pod deployment. With this update, labels are added to the dashboard `ConfigMap` to identify the upgraded deployment as the current owner so that it will not be removed.
29+
(link:https://issues.redhat.com/browse/LOG-6608[LOG-6608])
30+
31+
* Before this update, the logging `must-gather` did not collect resources such as `UIPlugin`, `ClusterLogForwarder`, `LogFileMetricExporter` and `LokiStack` CR. With this update, these resources are now collected in their namespace directory instead of the cluster-logging one.
32+
(link:https://issues.redhat.com/browse/LOG-6654[LOG-6654])
33+
34+
* Before this update, Vector did not retain process information, such as the program name, app-name, procID, and other details, when forwarding journal logs by using the syslog protocol. This could lead to the loss of important information. With this update, the Vector collector now preserves all required process information, and the data format adheres to the specifications of `RFC3164` and `RFC5424`.
35+
(link:https://issues.redhat.com/browse/LOG-6659[LOG-6659])

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

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

77
toc::[]
88

9+
include::modules/log6x-rn-6.0.4.adoc[leveloffset=+1]
10+
911
include::modules/log6x-rn-6.0.3.adoc[leveloffset=+1]
1012

1113
include::modules/log6x-rn-6.0.2.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)