|
| 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-2_{context}"] |
| 7 | += Logging 6.1.2 Release Notes |
| 8 | + |
| 9 | +This release includes link:https://access.redhat.com/errata/RHBA-2025:1229[{logging-uc} {for} Bug Fix Release 6.1.2]. |
| 10 | + |
| 11 | +[id="logging-release-notes-6-1-2-enhancements_{context}"] |
| 12 | +== New Features and Enhancements |
| 13 | + |
| 14 | +* 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. |
| 15 | +(link:https://issues.redhat.com/browse/LOG-6579[LOG-6579]) |
| 16 | + |
| 17 | +[id="logging-release-notes-6-1-2-bug-fixes_{context}"] |
| 18 | +== Bug Fixes |
| 19 | + |
| 20 | +* Before this update, the collector alerting rules contained summary and message fields. With this update, the collector alerting rules contain summary and description fields. |
| 21 | +(link:https://issues.redhat.com/browse/LOG-6126[LOG-6126]) |
| 22 | + |
| 23 | +* Before this update, the collector metrics dashboard could get removed after an operator upgrade due to a race condition during the transition 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. |
| 24 | +(link:https://issues.redhat.com/browse/LOG-6280[LOG-6280]) |
| 25 | + |
| 26 | +* Before this update, when you included infrastructure namespaces in application inputs, their `log_type` would be set to `application`. With this update, the `log_type` of infrastructure namespaces included in application inputs is set to `infrastructure`. |
| 27 | +(link:https://issues.redhat.com/browse/LOG-6373[LOG-6373]) |
| 28 | + |
| 29 | +* Before this update, the Cluster Logging 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 a cache. |
| 30 | +(link:https://issues.redhat.com/browse/LOG-6418[LOG-6418]) |
| 31 | + |
| 32 | +* Before this update, the logging `must-gather` did not collect resources such as `UIPlugin`, `ClusterLogForwarder`, `LogFileMetricExporter`, and `LokiStack`. With this update, the `must-gather` now collects all of these resources and places them in their respective namespace directory instead of the `cluster-logging` directory. |
| 33 | +(link:https://issues.redhat.com/browse/LOG-6422[LOG-6422]) |
| 34 | + |
| 35 | +* 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. |
| 36 | +(link:https://issues.redhat.com/browse/LOG-6506[LOG-6506]) |
| 37 | + |
| 38 | +* Before this update, the API documentation incorrectly claimed that `lokiStack` outputs would default the target namespace, which could prevent the collector from writing to that output. With this update, this claim has been removed from the API documentation and the Cluster Logging Operator now validates that a target namespace is present. |
| 39 | +(link:https://issues.redhat.com/browse/LOG-6573[LOG-6573]) |
| 40 | + |
| 41 | +* Before this update, the Cluster Logging Operator could deploy the collector with output configurations that were not referenced by any inputs. With this update, a validation check for the `ClusterLogForwarder` resource prevents the Operator from deploying the collector. |
| 42 | +(link:https://issues.redhat.com/browse/LOG-6585[LOG-6585]) |
| 43 | + |
| 44 | +[id="logging-release-notes-6-1-2-CVEs_{context}"] |
| 45 | +== CVEs |
| 46 | + |
| 47 | +* link:https://access.redhat.com/security/cve/CVE-2019-12900[CVE-2019-12900] |
0 commit comments