|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +// * backup_and_restore/oadp-1-4-release-notes.adoc |
| 4 | + |
| 5 | +:_mod-docs-content-type: REFERENCE |
| 6 | + |
| 7 | +[id="oadp-1-4-2-release-notes_{context}"] |
| 8 | += {oadp-short} 1.4.2 release notes |
| 9 | + |
| 10 | +The {oadp-first} 1.4.2 release notes lists new features, resolved issues and bugs, and known issues. |
| 11 | + |
| 12 | +[id="new-features-1-4-2_{context}"] |
| 13 | +== New features |
| 14 | + |
| 15 | +.Backing up different volumes in the same namespace by using the VolumePolicy feature is now possible |
| 16 | + |
| 17 | +With this release, Velero provides resource policies to back up different volumes in the same namespace by using the `VolumePolicy` feature. The supported `VolumePolicy` feature to back up different volumes includes `skip`, `snapshot`, and `fs-backup` actions. |
| 18 | +link:https://issues.redhat.com/browse/OADP-1071[OADP-1071] |
| 19 | + |
| 20 | +.File system backup and data mover can now use short-term credentials |
| 21 | + |
| 22 | +File system backup and data mover can now use short-term credentials such as {aws-short} {sts-first} and {gcp-short} WIF. With this support, backup is successfully completed without any `PartiallyFailed` status. |
| 23 | +link:https://issues.redhat.com/browse/OADP-5095[OADP-5095] |
| 24 | + |
| 25 | +[id="resolved-issues-1-4-2_{context}"] |
| 26 | +== Resolved issues |
| 27 | + |
| 28 | +.DPA now reports errors if VSL contains an incorrect provider value |
| 29 | + |
| 30 | +Previously, if the provider of a Volume Snapshot Location (VSL) spec was incorrect, the Data Protection Application (DPA) reconciled successfully. With this update, DPA reports errors and requests for a valid provider value. |
| 31 | +link:https://issues.redhat.com/browse/OADP-5044[OADP-5044] |
| 32 | + |
| 33 | +.Data Mover restore is successful irrespective of using different OADP namespaces for backup and restore |
| 34 | + |
| 35 | +Previously, when backup operation was executed by using {oadp-short} installed in one namespace but was restored by using {oadp-short} installed in a different namespace, the Data Mover restore failed. With this update, Data Mover restore is now successful. |
| 36 | +link:https://issues.redhat.com/browse/OADP-5460[OADP-5460] |
| 37 | + |
| 38 | +.SSE-C backup works with the calculated MD5 of the secret key |
| 39 | + |
| 40 | +Previously, backup failed with the following error: |
| 41 | +[source,terminal] |
| 42 | +---- |
| 43 | +Requests specifying Server Side Encryption with Customer provided keys must provide the client calculated MD5 of the secret key. |
| 44 | +---- |
| 45 | +With this update, missing Server-Side Encryption with Customer-Provided Keys (SSE-C) base64 and MD5 hash are now fixed. As a result, SSE-C backup works with the calculated MD5 of the secret key. In addition, incorrect `errorhandling` for the `customerKey` size is also fixed. |
| 46 | +link:https://issues.redhat.com/browse/OADP-5388[OADP-5388] |
| 47 | + |
| 48 | +For a complete list of all issues resolved in this release, see the list of link:https://issues.redhat.com/issues/?filter=12452476[OADP 1.4.2 resolved issues] in Jira. |
| 49 | + |
| 50 | + |
| 51 | +[id="known-issues-1-4-2_{context}"] |
| 52 | +== Known issues |
| 53 | + |
| 54 | +.The nodeSelector spec is not supported for the Data Mover restore action |
| 55 | + |
| 56 | +When a Data Protection Application (DPA) is created with the `nodeSelector` field set in the `nodeAgent` parameter, Data Mover restore partially fails instead of completing the restore operation. |
| 57 | +link:https://issues.redhat.com/browse/OADP-5260[OADP-5260] |
| 58 | + |
| 59 | +.The S3 storage does not use proxy environment when TLS skip verify is specified |
| 60 | + |
| 61 | +In the image registry backup, the S3 storage does not use the proxy environment when the `insecureSkipTLSVerify` parameter is set to `true`. |
| 62 | +link:https://issues.redhat.com/browse/OADP-3143[OADP-3143] |
| 63 | + |
| 64 | +.Kopia does not delete artifacts after backup expiration |
| 65 | + |
| 66 | +Even after you delete a backup, Kopia does not delete the volume artifacts from the `${bucket_name}/kopia/${namespace}` on the S3 location after backup expired. For more information, see "About Kopia repository maintenance". |
| 67 | +link:https://issues.redhat.com/browse/OADP-5131[OADP-5131] |
0 commit comments