You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: backup_and_restore/application_backup_and_restore/oadp-release-notes.adoc
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,8 @@ toc::[]
9
9
10
10
The release notes for OpenShift API for Data Protection (OADP) describe new features and enhancements, deprecated features, product recommendations, known issues, and resolved issues.
The new `resourceTimeout` option specifies the timeout duration in minutes for waiting on various Velero resources. This option applies to resources such as Velero CRD availability, `volumeSnapshot` deletion, and backup repository availability. The default duration is ten minutes.
14
+
.Resource timeouts
15
+
The new `resourceTimeout` option specifies the timeout duration in minutes for waiting on various Velero resources. This option applies to resources such as Velero CRD availability, `volumeSnapshot` deletion, and backup repository availability. The default duration is 10 minutes.
The OADP Data Mover enables you to back up Container Storage Interface (CSI) volume snapshots to a remote object store. When you enable Data Mover, you can restore stateful applications using CSI volume snapshots pulled from the object store in case of accidental cluster deletion, cluster failure, or data corruption.
25
25
26
26
:FeatureName: OADP Data Mover
@@ -34,5 +34,12 @@ For a complete list of all issues resolved in this release, see the list of link
34
34
[id="known-issues-1-2-0_{context}"]
35
35
== Known issues
36
36
37
-
This release does not have any known issues.
37
+
The following issues have been highlighted as known issues in the release of OADP 1.2.0:
38
38
39
+
.Multiple HTTP/2 enabled web servers are vulnerable to a DDoS attack (Rapid Reset Attack)
40
+
41
+
The HTTP/2 protocol is susceptible to a denial of service attack because request cancellation can reset multiple streams quickly. The server has 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 results in a denial of service due to server resource consumption. For a list of all OADP issues associated with this CVE, see the following link:https://issues.redhat.com/browse/OADP-2868?filter=12421248[Jira list].
42
+
43
+
It is advised to upgrade to OADP 1.2.3, which resolves this issue.
44
+
45
+
For more information, see link:https://access.redhat.com/security/cve/cve-2023-39325[CVE-2023-39325 (Rapid Reset Attack)].
There are no new features in the release of {oadp-first} 1.2.3.
14
+
15
+
// :FeatureName: OADP Data Mover
16
+
// include::snippets/technology-preview.adoc[]
17
+
18
+
[id="resolved-issues-1-2-3_{context}"]
19
+
== Resolved issues
20
+
21
+
The following highlighted issues are resolved in OADP 1.2.3:
22
+
23
+
24
+
.Multiple HTTP/2 enabled web servers are vulnerable to a DDoS attack (Rapid Reset Attack)
25
+
26
+
In previous releases of OADP 1.2, 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. For a list of all OADP issues associated with this CVE, see the following link:https://issues.redhat.com/browse/OADP-2868?filter=12421248[Jira list].
27
+
28
+
For more information, see link:https://access.redhat.com/security/cve/cve-2023-39325[CVE-2023-39325 (Rapid Reset Attack)].
29
+
30
+
31
+
For a complete list of all issues resolved in the release of OADP 1.2.3, see the list of link:https://issues.redhat.com/browse/OADP-2094?filter=12422262[OADP 1.2.3 resolved issues] in Jira.
32
+
33
+
34
+
[id="known-issues-1-2-3_{context}"]
35
+
== Known issues
36
+
37
+
There are no known issues in the release of OADP 1.2.3.
0 commit comments