Merge pull request #34814 from rolfedh/RHDEVDOCS-3179

Preeticp · web-flow · commit 662547c7a465 · 2021-07-27T17:18:27.000+05:30
RHDEVDOCS-3179 Update release notes for 5.0.6
diff --git a/logging/cluster-logging-release-notes.adoc b/logging/cluster-logging-release-notes.adoc
@@ -11,7 +11,7 @@ toc::[]
 The following advisories are available for {ProductName}:
 
 * link:https://access.redhat.com/errata/RHBA-2021:2112[RHBA-2021:2112 - Bug Fix Advisory. OpenShift Logging Bug Fix Release 5.1.0]
-//* link:https://access.redhat.com/errata/RHBA-2021:2655[RHBA-2021:2655 - Bug Fix Advisory. Openshift Logging Bug Fix Release (5.0.6)]
+* link:https://access.redhat.com/errata/RHBA-2021:2655[RHBA-2021:2655 - Bug Fix Advisory. Openshift Logging Bug Fix Release (5.0.6)]
 * link:https://access.redhat.com/errata/RHSA-2021:2374[RHSA-2021:2374 - Security Advisory. Moderate: Openshift Logging Bug Fix Release (5.0.5)]
 * link:https://access.redhat.com/errata/RHSA-2021:2136[RHSA-2021:2136 - Security Advisory. Moderate: Openshift Logging security and bugs update (5.0.4)]
 * link:https://access.redhat.com/errata/RHSA-2021:1515[RHSA-2021:1515 - Security Advisory. Important OpenShift Logging Bug Fix Release (5.0.3)]
@@ -32,7 +32,7 @@ Red Hat is committed to replacing problematic language in our code, documentatio
 
 // Release Notes by version
 include::modules/cluster-logging-release-notes-5.1.0.adoc[leveloffset=+1]
-// include::modules/cluster-logging-release-notes-5.0.6.adoc[leveloffset=+1]
+include::modules/cluster-logging-release-notes-5.0.6.adoc[leveloffset=+1]
 include::modules/cluster-logging-release-notes-5.0.5.adoc[leveloffset=+1]
 include::modules/cluster-logging-release-notes-5.0.4.adoc[leveloffset=+1]
 include::modules/cluster-logging-release-notes-5.0.3.adoc[leveloffset=+1]
diff --git a/modules/cluster-logging-release-notes-5.0.6.adoc b/modules/cluster-logging-release-notes-5.0.6.adoc
@@ -8,23 +8,61 @@ This release includes link:https://access.redhat.com/errata/RHBA-2021:2655[RHBA-
 
 This release also includes the following bug fixes:
 
-* LOG-1451 [1927249] fieldmanager.go:186] [SHOULD NOT HAPPEN] failed to update managedFields...duplicate entries for key [name="POLICY_MAPPING"] (link:https://issues.redhat.com/browse/LOG-1451[*LOG-1451*])
-* LOG-1537 Full Cluster Cert Redeploy is broken when the ES clusters includes non-data nodes(link:https://issues.redhat.com/browse/LOG-1537[*LOG-1537*])
-* LOG-1430 eventrouter raising "Observed a panic: &runtime.TypeAssertionError" (link:https://issues.redhat.com/browse/LOG-1430[*LOG-1430*])
+* LOG-1451 - [1927249] fieldmanager.go:186] [SHOULD NOT HAPPEN] failed to update managedFields...duplicate entries for key [name="POLICY_MAPPING"] (link:https://issues.redhat.com/browse/LOG-1451[*LOG-1451*])
+* LOG-1537 - Full Cluster Cert Redeploy is broken when the ES clusters includes non-data nodes(link:https://issues.redhat.com/browse/LOG-1537[*LOG-1537*])
+* LOG-1430 - eventrouter raising "Observed a panic: &runtime.TypeAssertionError" (link:https://issues.redhat.com/browse/LOG-1430[*LOG-1430*])
+* LOG-1461 - The index management job status is always `Completed` even when there has an error in the job log. (link:https://issues.redhat.com/browse/LOG-1461[*LOG-1461*])
+* LOG-1459 - Operators missing disconnected annotation (link:https://issues.redhat.com/browse/LOG-1459[*LOG-1459*])
+* LOG-1572 - Bug 1981579: Fix built-in application behavior to collect all of logs (link:https://issues.redhat.com/browse/LOG-1572[*LOG-1572*])
 
-[id="openshift-logging-5-0-6-references"]
-== References
 
-* https://access.redhat.com/security/cve/CVE-2018-25011
-* https://access.redhat.com/security/cve/CVE-2020-26541
-* https://access.redhat.com/security/cve/CVE-2020-36328
-* https://access.redhat.com/security/cve/CVE-2020-36329
-* https://access.redhat.com/security/cve/CVE-2021-3516
-* https://access.redhat.com/security/cve/CVE-2021-3517
-* https://access.redhat.com/security/cve/CVE-2021-3518
-* https://access.redhat.com/security/cve/CVE-2021-3520
-* https://access.redhat.com/security/cve/CVE-2021-3537
-* https://access.redhat.com/security/cve/CVE-2021-3541
-* https://access.redhat.com/security/cve/CVE-2021-20271
-* https://access.redhat.com/security/cve/CVE-2021-27219
-* https://access.redhat.com/security/cve/CVE-2021-33034
+[id="openshift-logging-5-0-6-cves"]
+== CVEs
+
+* link:https://access.redhat.com/security/cve/CVE-2016-10228[CVE-2016-10228]
+* link:https://access.redhat.com/security/cve/CVE-2017-14502[CVE-2017-14502]
+* link:https://access.redhat.com/security/cve/CVE-2018-25011[CVE-2018-25011]
+* link:https://access.redhat.com/security/cve/CVE-2019-2708[CVE-2019-2708]
+* link:https://access.redhat.com/security/cve/CVE-2019-9169[CVE-2019-9169]
+* link:https://access.redhat.com/security/cve/CVE-2019-25013[CVE-2019-25013]
+* link:https://access.redhat.com/security/cve/CVE-2020-8231[CVE-2020-8231]
+* link:https://access.redhat.com/security/cve/CVE-2020-8284[CVE-2020-8284]
+* link:https://access.redhat.com/security/cve/CVE-2020-8285[CVE-2020-8285]
+* link:https://access.redhat.com/security/cve/CVE-2020-8286[CVE-2020-8286]
+* link:https://access.redhat.com/security/cve/CVE-2020-8927[CVE-2020-8927]
+* link:https://access.redhat.com/security/cve/CVE-2020-10543[CVE-2020-10543]
+* link:https://access.redhat.com/security/cve/CVE-2020-10878[CVE-2020-10878]
+* link:https://access.redhat.com/security/cve/CVE-2020-13434[CVE-2020-13434]
+* link:https://access.redhat.com/security/cve/CVE-2020-14344[CVE-2020-14344]
+* link:https://access.redhat.com/security/cve/CVE-2020-14345[CVE-2020-14345]
+* link:https://access.redhat.com/security/cve/CVE-2020-14346[CVE-2020-14346]
+* link:https://access.redhat.com/security/cve/CVE-2020-14347[CVE-2020-14347]
+* link:https://access.redhat.com/security/cve/CVE-2020-14360[CVE-2020-14360]
+* link:https://access.redhat.com/security/cve/CVE-2020-14361[CVE-2020-14361]
+* link:https://access.redhat.com/security/cve/CVE-2020-14362[CVE-2020-14362]
+* link:https://access.redhat.com/security/cve/CVE-2020-14363[CVE-2020-14363]
+* link:https://access.redhat.com/security/cve/CVE-2020-15358[CVE-2020-15358]
+* link:https://access.redhat.com/security/cve/CVE-2020-25712[CVE-2020-25712]
+* link:https://access.redhat.com/security/cve/CVE-2020-26116[CVE-2020-26116]
+* link:https://access.redhat.com/security/cve/CVE-2020-26137[CVE-2020-26137]
+* link:https://access.redhat.com/security/cve/CVE-2020-26541[CVE-2020-26541]
+* link:https://access.redhat.com/security/cve/CVE-2020-27618[CVE-2020-27618]
+* link:https://access.redhat.com/security/cve/CVE-2020-27619[CVE-2020-27619]
+* link:https://access.redhat.com/security/cve/CVE-2020-28196[CVE-2020-28196]
+* link:https://access.redhat.com/security/cve/CVE-2020-29361[CVE-2020-29361]
+* link:https://access.redhat.com/security/cve/CVE-2020-29362[CVE-2020-29362]
+* link:https://access.redhat.com/security/cve/CVE-2020-29363[CVE-2020-29363]
+* link:https://access.redhat.com/security/cve/CVE-2020-36328[CVE-2020-36328]
+* link:https://access.redhat.com/security/cve/CVE-2020-36329[CVE-2020-36329]
+* link:https://access.redhat.com/security/cve/CVE-2021-3177[CVE-2021-3177]
+* link:https://access.redhat.com/security/cve/CVE-2021-3326[CVE-2021-3326]
+* link:https://access.redhat.com/security/cve/CVE-2021-3516[CVE-2021-3516]
+* link:https://access.redhat.com/security/cve/CVE-2021-3517[CVE-2021-3517]
+* link:https://access.redhat.com/security/cve/CVE-2021-3518[CVE-2021-3518]
+* link:https://access.redhat.com/security/cve/CVE-2021-3520[CVE-2021-3520]
+* link:https://access.redhat.com/security/cve/CVE-2021-3537[CVE-2021-3537]
+* link:https://access.redhat.com/security/cve/CVE-2021-3541[CVE-2021-3541]
+* link:https://access.redhat.com/security/cve/CVE-2021-20271[CVE-2021-20271]
+* link:https://access.redhat.com/security/cve/CVE-2021-23336[CVE-2021-23336]
+* link:https://access.redhat.com/security/cve/CVE-2021-27219[CVE-2021-27219]
+* link:https://access.redhat.com/security/cve/CVE-2021-33034[CVE-2021-33034]
diff --git a/modules/cluster-logging-release-notes-5.1.0.adoc b/modules/cluster-logging-release-notes-5.1.0.adoc
@@ -80,5 +80,5 @@ If you configure the `ClusterLogging` custom resource (CR) to switch from epheme
 +
 (link:https://issues.redhat.com/browse/LOG-1351[*LOG-1351*])
 
-Before this update, if you redeployed a full Elasticsearch cluster, it got stuck in an unhealthy state, with one non-data node running and all other data nodes shut down. This happened because new certificates prevented the Elasticsearch Operator from scaling down the non-data nodes of the Elasticsearch cluster. With this update, Elasticsearch Operator can scale all the data and non-data nodes down and then back up again, so they load the new certificates. The Elasticsearch Operator can reach the new nodes after they load the new certificates.
+* Before this update, if you redeployed a full Elasticsearch cluster, it got stuck in an unhealthy state, with one non-data node running and all other data nodes shut down. This issue happened because new certificates prevented the Elasticsearch Operator from scaling down the non-data nodes of the Elasticsearch cluster. With this update, Elasticsearch Operator can scale all the data and non-data nodes down and then back up again, so they load the new certificates. The Elasticsearch Operator can reach the new nodes after they load the new certificates.
 (link:https://issues.redhat.com/browse/LOG-1536[*LOG-1536*])

Original file line number	Diff line number	Diff line change
@@ -80,5 +80,5 @@ If you configure the `ClusterLogging` custom resource (CR) to switch from epheme
`80`	`80`	`+`
`81`	`81`	`(link:https://issues.redhat.com/browse/LOG-1351[LOG-1351])`
`82`	`82`
`83`		-Before this update, if you redeployed a full Elasticsearch cluster, it got stuck in an unhealthy state, with one non-data node running and all other data nodes shut down. This happened because new certificates prevented the Elasticsearch Operator from scaling down the non-data nodes of the Elasticsearch cluster. With this update, Elasticsearch Operator can scale all the data and non-data nodes down and then back up again, so they load the new certificates. The Elasticsearch Operator can reach the new nodes after they load the new certificates.
	`83`	+* Before this update, if you redeployed a full Elasticsearch cluster, it got stuck in an unhealthy state, with one non-data node running and all other data nodes shut down. This issue happened because new certificates prevented the Elasticsearch Operator from scaling down the non-data nodes of the Elasticsearch cluster. With this update, Elasticsearch Operator can scale all the data and non-data nodes down and then back up again, so they load the new certificates. The Elasticsearch Operator can reach the new nodes after they load the new certificates.
`84`	`84`	`(link:https://issues.redhat.com/browse/LOG-1536[LOG-1536])`