|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +// * backup_and_restore/oadp-release-notes-1-3.adoc |
| 4 | + |
| 5 | +:_mod-docs-content-type: REFERENCE |
| 6 | +[id="oadp-release-notes-1-3-1_{context}"] |
| 7 | += OADP 1.3.1 release notes |
| 8 | + |
| 9 | +The {oadp-first} 1.3.1 release notes lists new features and resolved issues. |
| 10 | + |
| 11 | +[id="new-features-1-3-1_{context}"] |
| 12 | +== New features |
| 13 | + |
| 14 | +.OADP 1.3.0 Data Mover is now fully supported |
| 15 | + |
| 16 | +The OADP built-in Data Mover, introduced in OADP 1.3.0 as a Technology Preview, is now fully supported for both containerized and virtual machine workloads. |
| 17 | + |
| 18 | +[id="resolved-issues-1-3-1_{context}"] |
| 19 | +== Resolved issues |
| 20 | + |
| 21 | +.{ibm-cloud-name} Object Storage is now supported as a backup storage provider |
| 22 | + |
| 23 | +{ibm-cloud-name} Object Storage is one of the AWS S3 compatible backup storage providers, which was unsupported previously. |
| 24 | +With this update, {ibm-cloud-name} Object Storage is now supported as an AWS S3 compatible backup storage provider. |
| 25 | + |
| 26 | +link:https://issues.redhat.com/browse/OADP-3788[OADP-3788] |
| 27 | + |
| 28 | +.OADP operator now correctly reports the missing region error |
| 29 | + |
| 30 | +Previously, when you specified `profile:default` without specifying the `region` in the AWS Backup Storage Location (BSL) configuration, the OADP operator failed to report the `missing region` error on the Data Protection Application (DPA) custom resource (CR). This update corrects validation of DPA BSL specification for AWS. As a result, the OADP Operator reports the `missing region` error. |
| 31 | + |
| 32 | +link:https://issues.redhat.com/browse/OADP-3044[OADP-3044] |
| 33 | + |
| 34 | +.Custom labels are not removed from the openshift-adp namespace |
| 35 | + |
| 36 | +Previously, the `openshift-adp-controller-manager` pod would reset the labels attached to the `openshift-adp` namespace. This caused synchronization issues for applications requiring custom labels such as Argo CD, leading to improper functionality. With this update, this issue is fixed and custom labels are not removed from the `openshift-adp` namespace. |
| 37 | + |
| 38 | +link:https://issues.redhat.com/browse/OADP-3189[OADP-3189] |
| 39 | + |
| 40 | +.OADP must-gather image collects CRDs |
| 41 | + |
| 42 | +Previously, the OADP `must-gather` image did not collect the custom resource definitions (CRDs) shipped by OADP. Consequently, you could not use the `omg` tool to extract data in the support shell. |
| 43 | +With this fix, the `must-gather` image now collects CRDs shipped by OADP and can use the `omg` tool to extract data. |
| 44 | + |
| 45 | +link:https://issues.redhat.com/browse/OADP-3229[OADP-3229] |
| 46 | + |
| 47 | +.Garbage collection has the correct description for the default frequency value |
| 48 | + |
| 49 | +Previously, the `garbage-collection-frequency` field had a wrong description for the default frequency value. With this update, `garbage-collection-frequency` has a correct value of one hour for the `gc-controller` reconciliation default frequency. |
| 50 | + |
| 51 | +link:https://issues.redhat.com/browse/OADP-3486[OADP-3486] |
| 52 | + |
| 53 | +.FIPS Mode flag is available in OperatorHub |
| 54 | + |
| 55 | +By setting the `fips-compliant` flag to `true`, the FIPS mode flag is now added to the OADP Operator listing in OperatorHub. This feature was enabled in OADP 1.3.0 but did not show up in the Red Hat Container catalog as being FIPS enabled. |
| 56 | + |
| 57 | +link:https://issues.redhat.com/browse/OADP-3495[OADP-3495] |
| 58 | + |
| 59 | +.CSI plugin does not panic with a nil pointer when csiSnapshotTimeout is set to a short duration |
| 60 | + |
| 61 | +Previously, when the `csiSnapshotTimeout` parameter was set to a short duration, the CSI plugin encountered the following error: `plugin panicked: runtime error: invalid memory address or nil pointer dereference`. |
| 62 | + |
| 63 | +With this fix, the backup fails with the following error: `Timed out awaiting reconciliation of volumesnapshot`. |
| 64 | + |
| 65 | +link:https://issues.redhat.com/browse/OADP-3069[OADP-3069] |
| 66 | + |
| 67 | + |
| 68 | +For a complete list of all issues resolved in this release, see the list of link:https://issues.redhat.com/issues/?filter=12432794[OADP 1.3.1 resolved issues] in Jira. |
| 69 | + |
| 70 | +[id="known-issues-1-3-1_{context}"] |
| 71 | +== Known issues |
| 72 | + |
| 73 | +.Backup and storage restrictions for {sno-caps} clusters deployed on {ibm-power-name} and {ibm-z-name} platforms |
| 74 | + |
| 75 | +Review the following backup and storage related restrictions for {sno-caps} clusters that are deployed on {ibm-power-name} and {ibm-z-name} platforms: |
| 76 | + |
| 77 | +Storage:: Only NFS storage is currently compatible with {sno} clusters deployed on {ibm-power-name} and {ibm-z-name} platforms. |
| 78 | +Backup:: Only the backing up applications with File System Backup such as `kopia` and `restic` are supported for backup and restore operations. |
| 79 | + |
| 80 | +link:https://issues.redhat.com/browse/OADP-3787[OADP-3787] |
| 81 | + |
| 82 | +.Cassandra application pods enter in the CrashLoopBackoff status after restoring OADP |
| 83 | + |
| 84 | +After OADP restores, the Cassandra application pods might enter in the `CrashLoopBackoff` status. To work around this problem, delete the `StatefulSet` pods with any error or the `CrashLoopBackoff` state after restoring OADP. The `StatefulSet` controller recreates these pods and it runs normally. |
| 85 | + |
| 86 | +link:https://issues.redhat.com/browse/OADP-3767[OADP-3767] |
0 commit comments