More known issues

Author: CarmiWisemon

modules/oadp-release-notes-1-3-0.adoc

@@ -71,8 +71,8 @@ During interoperability testing, Red Hat OpenShift Container Platform 4.14 had t
 There was a regresssion in Pod Volume Backup (PVB) functionality when Velero was installed in several namespaces. The pod volume backup controller was not properly limiting itself to PVBs in its own namespace.
 link:https://issues.redhat.com/browse/OADP-2308[OADP-2308]
 
-.CVE-2023-39325 A flaw was found in handling multiplexed streams in the HTTP/2 protocol.
-A flaw was found in handling multiplexed streams in the HTTP/2 protocol. In previous releases of OADP, a client could repeatedly make a request for a new multiplex stream and immediately send an RST_STREAM frame to cancel it. This created extra work for the server setting up and tearing down the streams while not hitting any server-side limit for the maximum number of active streams per connection, which resulted in a denial of service due to server resource consumption.
+.CVE-2023-39325 Multiple HTTP/2 enabled web servers are vulnerable to a DDoS attack (Rapid Reset Attack)
+In previous releases of OADP, the HTTP/2 protocol was susceptible to a denial of service attack because request cancellation could reset multiple streams quickly. The server had to set up and tear down the streams while not hitting any server-side limit for the maximum number of active streams per connection. This resulted in a denial of service due to server resource consumption
 
 The following issues have been listed under this issue:
 
@@ -90,7 +90,7 @@ The following issues have been listed under this issue:
 For more information, see link:https://access.redhat.com/security/cve/cve-2023-39325[CVE-2023-39325 (Rapid Reset Attack)]
 
 
-For a complete list of all issues resolved in this release, see the list of link:https://issues.redhat.com/browse/OADP-2819?filter=12422837[OADP 1.3.0 resolved issues] in Jira.
+For a complete list of all issues resolved in this release, see the list of link:https://issues.redhat.com/issues/?filter=12422837[OADP 1.3.0 resolved issues] in Jira.
 
 [id="known-issues-1-3-0_{context}"]
 == Known issues
@@ -99,16 +99,20 @@ For a complete list of all issues resolved in this release, see the list of link
 The CSI plugin panics on nil pointer when `csiSnapshotTimeout` is set to a short duration. Sometimes it succeeds to complete the snapshot within a short duration, but often it panics with the backup `PartiallyFailed` with the following error: `plugin panicked: runtime error: invalid memory address or nil pointer dereference`. link:https://issues.redhat.com/browse/OADP-3069[OADP-3069]
 
 .Backup is marked as PartiallyFailed when volumeSnapshotContent CR has an error
-If any of the `VolumeSnapshotContent` CR has an error related to removing `VolumeSnapshotBeingCreated` annotation it moves backup to `WaitingForPluginOperationsPartiallyFailed` phase. link:https://issues.redhat.com/browse/OADP-2871[OADP-2871]
+If any of the `VolumeSnapshotContent` CRs have an error related to removing the `VolumeSnapshotBeingCreated` annotation, it moves the backup to the `WaitingForPluginOperationsPartiallyFailed` phase. link:https://issues.redhat.com/browse/OADP-2871[OADP-2871]
 
 .Performance issues when restoring 30k resources for the first time
-When restoring for the first time, without an existing-resource-policy, it takes twice as long as when restoring the second and third time, with an existing-resource-policy. link:https://issues.redhat.com/browse/OADP-3071[OADP-3071]
+When restoring 30k resources for the first time, without an existing-resource-policy, it takes twice as long to restore them, then it takes during the second and third try, with an existing-resource-policy. link:https://issues.redhat.com/browse/OADP-3071[OADP-3071]
 
 .Post Restore Hooks might start running before Datadownload operation has released the related PV
-Due to the Asynchronous nature of the Data Mover operation a post-hook might be attempted before the related pods PV's are released by the Data Mover PVC.
+Due to the asynchronous nature of the Data Mover operation, a post-hook might be attempted, before the related pods PV's are released by the Data Mover PVC.
 link:https://issues.redhat.com/browse/OADP-3067[OADP-3067]
 
-For a complete list of all known issues in this release, see the list of link:https://issues.redhat.com/browse/OADP-2688?filter=12422838[OADP 1.3.0 known issues] in Jira.
+.GCP-Workload Identity Federation VSL backup PartiallyFailed
+VSL backup `PartiallyFailed` when GCP workload identity is configured on GCP.
+link:https://issues.redhat.com/browse/OADP-3084[OADP-3084]
+
+For a complete list of all known issues in this release, see the list of link:https://issues.redhat.com/issues/?filter=12422838[OADP 1.3.0 known issues] in Jira.
 
 [id="upgrade-notes-1-3-0_{context}"]
 == Upgrade notes
@@ -305,18 +309,14 @@ dpa-sample-1   Available   1s               3d16h   true
 
 . Verify that the `PHASE` is in `Available`.
 
-////
-The continuation from this point and on isn't in the XREF
-////
+In OADP 1.3 you can start data movement off cluster per backup vs. creating a DataProtectionApplication (DPA) configuration.
 
-. In OADP 1.3 you can start data movement off cluster per backup vs. creating a DataProtectionApplication (DPA) configuration.
-+
 .Example
 [source,terminal]
 ----
 velero backup create example-backup --include-namespaces mysql-persistent --snapshot-move-data=true
 ----
-+
+
 .Example
 [source,yaml]
 ----