diff --git a/modules/coo-rel-notes-152.adoc b/modules/coo-rel-notes-152.adoc new file mode 100644 index 00000000000..f5883a95f5e --- /dev/null +++ b/modules/coo-rel-notes-152.adoc @@ -0,0 +1,83 @@ +//Module included in the following assemblies: +// +// * release-notes/cluster-observability-operator-release-notes.adoc + +:_mod-docs-content-type: REFERENCE + +[id="cluster-observability-operator-release-notes-1-5-2_{context}"] += {coo-full} 1.5.2 + +[role="_abstract"] +Review the release notes for {coo-full} version 1.5.2, including fixed issues and security advisories for each minor release. + +The following advisory is available for {coo-full} 1.5.2: + +* link:https://access.redhat.com/errata/RHSA-2026:61314[RHSA-2026:61314] {coo-full} 1.5.2 + +[id="cluster-observability-operator-1-5-2-fixed-issues_{context}"] +== Fixed issues + +Monitoring UI plugin reconciles successfully when Console branding is configured:: + +Before this update, the monitoring UI plugin reconciler's merger logic inadvertently included the `customLogoFile` field as a zero value when patching the Console resource that had `spec.customization.logos` configured. As a consequence, the API server rejected the patch due to mutual exclusivity validation between `logos` and `customLogoFile`, causing the UI plugin to enter a `Degraded` state with a `UIPluginFailedToReconcile` error. This prevented the `monitoring-console-plugin` from being registered in the console's enabled plugins list, and Perses dashboards were not visible in the UI. ++ +With this release, the operator's merger logic properly handles Console resource patches without including zero-value fields. As a result, the UI plugin reconciles successfully, the `monitoring-console-plugin` is registered in the enabled plugins list, and Perses dashboards are visible in the console UI. ++ +link:https://issues.redhat.com/browse/COO-1973[COO-1973] + +Health analyzer metrics endpoint no longer fails due to duplicate metric collection:: + +Before this update, the health analyzer component generated duplicate `component_health_alert` metrics with identical label sets when alerts fired from multiple sources that lacked distinguishing labels. As a consequence, the `/metrics` endpoint returned HTTP 500 errors, causing Prometheus to mark the health analyzer ServiceMonitor target as fully down and trigger `TargetDown` alerts. ++ +With this release, the health analyzer includes distinguishing labels in metric collection to prevent duplicate metric identities. As a result, the `/metrics` endpoint returns successfully and Prometheus can scrape the target without errors. ++ +link:https://issues.redhat.com/browse/COO-1964[COO-1964] + +Perses pod no longer crashes when using deprecated web listen address flag:: + +Before this update, the Perses component used the deprecated `-web.listen-address` command-line flag to configure its listening address. This flag was not recognized by the updated Perses binary. As a consequence, the `perses-0` pod entered a `CrashLoopBackOff` state and failed to start. ++ +With this release, the Perses configuration uses the supported `-config` flag with proper YAML configuration. As a result, the Perses pod starts successfully and operates normally. ++ +link:https://issues.redhat.com/browse/COO-2184[COO-2184] + +[id="cluster-observability-operator-1-5-2-CVEs_{context}"] +== CVEs + +* link:https://access.redhat.com/security/cve/cve-2026-56852[CVE-2026-56852] + +* link:https://access.redhat.com/security/cve/cve-2026-55677[CVE-2026-55677] + +* link:https://access.redhat.com/security/cve/cve-2026-46600[CVE-2026-46600] + +* link:https://access.redhat.com/security/cve/cve-2026-46597[CVE-2026-46597] + +* link:https://access.redhat.com/security/cve/cve-2026-46595[CVE-2026-46595] + +* link:https://access.redhat.com/security/cve/cve-2026-44740[CVE-2026-44740] + +* link:https://access.redhat.com/security/cve/cve-2026-42508[CVE-2026-42508] + +* link:https://access.redhat.com/security/cve/cve-2026-41178[CVE-2026-41178] + +* link:https://access.redhat.com/security/cve/cve-2026-39832[CVE-2026-39832] + +* link:https://access.redhat.com/security/cve/cve-2026-39831[CVE-2026-39831] + +* link:https://access.redhat.com/security/cve/cve-2026-39830[CVE-2026-39830] + +* link:https://access.redhat.com/security/cve/cve-2026-39829[CVE-2026-39829] + +* link:https://access.redhat.com/security/cve/cve-2026-35469[CVE-2026-35469] + +* link:https://access.redhat.com/security/cve/cve-2026-32285[CVE-2026-32285] + +* link:https://access.redhat.com/security/cve/cve-2026-32281[CVE-2026-32281] + +* link:https://access.redhat.com/security/cve/cve-2026-29181[CVE-2026-29181] + +* link:https://access.redhat.com/security/cve/cve-2026-27145[CVE-2026-27145] + +* link:https://access.redhat.com/security/cve/cve-2026-13676[CVE-2026-13676] + +* link:https://access.redhat.com/security/cve/cve-2026-73643[CVE-2026-73643] diff --git a/release-notes/cluster-observability-operator-release-notes.adoc b/release-notes/cluster-observability-operator-release-notes.adoc index ef162756fd7..6e177d7c542 100644 --- a/release-notes/cluster-observability-operator-release-notes.adoc +++ b/release-notes/cluster-observability-operator-release-notes.adoc @@ -14,6 +14,8 @@ include::modules/coo-features.adoc[leveloffset=+1] include::snippets/unified-perspective-web-console.adoc[] +include::modules/coo-rel-notes-152.adoc[leveloffset=+1] + include::modules/coo-rel-notes-151.adoc[leveloffset=+1] include::modules/coo-rel-notes-150.adoc[leveloffset=+1]