RHDEVDOCS-5270 - Logging 5.5.11 Release Notes

Author: libander

logging/cluster-logging-release-notes.adoc

@@ -25,6 +25,8 @@ include::modules/cluster-logging-rn-5.6.1.adoc[leveloffset=+1]
 
 include::modules/cluster-logging-rn-5.6.adoc[leveloffset=+1]
 
+include::modules/logging-rn-5.5.11.adoc[leveloffset=+1]
+
 include::modules/cluster-logging-rn-5.5.10.adoc[leveloffset=+1]
 
 include::modules/cluster-logging-rn-5.5.9.adoc[leveloffset=+1]

logging/v5_5/logging-5-5-release-notes.adoc

@@ -8,6 +8,8 @@ toc::[]
 
 include::snippets/logging-compatibility-snip.adoc[]
 
+include::modules/logging-rn-5.5.11.adoc[leveloffset=+1]
+
 include::modules/logging-rn-5.5.10.adoc[leveloffset=+1]
 
 include::modules/logging-rn-5.5.9.adoc[leveloffset=+1]

modules/logging-rn-5.5.11.adoc

@@ -0,0 +1,66 @@
+// Module included in the following assemblies:
+//
+// logging-5-7-release-notes.adoc
+// cluster-logging-release-notes.adoc
+:_content-type: REFERENCE
+[id="logging-release-notes-5-5-11_{context}"]
+= Logging 5.5.11
+This release includes link:https://access.redhat.com/errata/RHBA-2023:3196[OpenShift Logging Bug Fix Release 5.5.11].
+
+[id="logging-5-5-11-bug-fixes_{context}"]
+== Bug fixes
+* Before this update, a time range could not be selected in the {Product-Title} web console by clicking and dragging over the logs histogram. With this update, clicking and dragging can be used to successfully select a time range. (link:https://issues.redhat.com/browse/LOG-4102[LOG-4102])
+
+* Before this update, clicking on the *Show Resources* link in the {Product-Title} web console did not produce any effect. With this update, the issue is resolved by fixing the functionality of the *Show Resources* link to toggle the display of resources for each log entry. (link:https://issues.redhat.com/browse/LOG-4117[LOG-4117])
+
+[id="logging-5-5-11-CVEs_{context}"]
+== CVEs
+* link:https://access.redhat.com/security/cve/CVE-2021-26341[CVE-2021-26341]
+* link:https://access.redhat.com/security/cve/CVE-2021-33655[CVE-2021-33655]
+* link:https://access.redhat.com/security/cve/CVE-2021-33656[CVE-2021-33656]
+* link:https://access.redhat.com/security/cve/CVE-2022-1462[CVE-2022-1462]
+* link:https://access.redhat.com/security/cve/CVE-2022-1679[CVE-2022-1679]
+* link:https://access.redhat.com/security/cve/CVE-2022-1789[CVE-2022-1789]
+* link:https://access.redhat.com/security/cve/CVE-2022-2196[CVE-2022-2196]
+* link:https://access.redhat.com/security/cve/CVE-2022-2663[CVE-2022-2663]
+* link:https://access.redhat.com/security/cve/CVE-2022-2795[CVE-2022-2795]
+* link:https://access.redhat.com/security/cve/CVE-2022-3028[CVE-2022-3028]
+* link:https://access.redhat.com/security/cve/CVE-2022-3239[CVE-2022-3239]
+* link:https://access.redhat.com/security/cve/CVE-2022-3522[CVE-2022-3522]
+* link:https://access.redhat.com/security/cve/CVE-2022-3524[CVE-2022-3524]
+* link:https://access.redhat.com/security/cve/CVE-2022-3564[CVE-2022-3564]
+* link:https://access.redhat.com/security/cve/CVE-2022-3566[CVE-2022-3566]
+* link:https://access.redhat.com/security/cve/CVE-2022-3567[CVE-2022-3567]
+* link:https://access.redhat.com/security/cve/CVE-2022-3619[CVE-2022-3619]
+* link:https://access.redhat.com/security/cve/CVE-2022-3623[CVE-2022-3623]
+* link:https://access.redhat.com/security/cve/CVE-2022-3625[CVE-2022-3625]
+* link:https://access.redhat.com/security/cve/CVE-2022-3627[CVE-2022-3627]
+* link:https://access.redhat.com/security/cve/CVE-2022-3628[CVE-2022-3628]
+* link:https://access.redhat.com/security/cve/CVE-2022-3707[CVE-2022-3707]
+* link:https://access.redhat.com/security/cve/CVE-2022-3970[CVE-2022-3970]
+* link:https://access.redhat.com/security/cve/CVE-2022-4129[CVE-2022-4129]
+* link:https://access.redhat.com/security/cve/CVE-2022-20141[CVE-2022-20141]
+* link:https://access.redhat.com/security/cve/CVE-2022-24765[CVE-2022-24765]
+* link:https://access.redhat.com/security/cve/CVE-2022-25265[CVE-2022-25265]
+* link:https://access.redhat.com/security/cve/CVE-2022-29187[CVE-2022-29187]
+* link:https://access.redhat.com/security/cve/CVE-2022-30594[CVE-2022-30594]
+* link:https://access.redhat.com/security/cve/CVE-2022-36227[CVE-2022-36227]
+* link:https://access.redhat.com/security/cve/CVE-2022-39188[CVE-2022-39188]
+* link:https://access.redhat.com/security/cve/CVE-2022-39189[CVE-2022-39189]
+* link:https://access.redhat.com/security/cve/CVE-2022-39253[CVE-2022-39253]
+* link:https://access.redhat.com/security/cve/CVE-2022-39260[CVE-2022-39260]
+* link:https://access.redhat.com/security/cve/CVE-2022-41218[CVE-2022-41218]
+* link:https://access.redhat.com/security/cve/CVE-2022-41674[CVE-2022-41674]
+* link:https://access.redhat.com/security/cve/CVE-2022-42703[CVE-2022-42703]
+* link:https://access.redhat.com/security/cve/CVE-2022-42720[CVE-2022-42720]
+* link:https://access.redhat.com/security/cve/CVE-2022-42721[CVE-2022-42721]
+* link:https://access.redhat.com/security/cve/CVE-2022-42722[CVE-2022-42722]
+* link:https://access.redhat.com/security/cve/CVE-2022-43750[CVE-2022-43750]
+* link:https://access.redhat.com/security/cve/CVE-2022-47929[CVE-2022-47929]
+* link:https://access.redhat.com/security/cve/CVE-2023-0394[CVE-2023-0394]
+* link:https://access.redhat.com/security/cve/CVE-2023-0461[CVE-2023-0461]
+* link:https://access.redhat.com/security/cve/CVE-2023-1195[CVE-2023-1195]
+* link:https://access.redhat.com/security/cve/CVE-2023-1582[CVE-2023-1582]
+* link:https://access.redhat.com/security/cve/CVE-2023-2491[CVE-2023-2491]
+* link:https://access.redhat.com/security/cve/CVE-2023-23454[CVE-2023-23454]
+* link:https://access.redhat.com/security/cve/CVE-2023-27535[CVE-2023-27535]