Fixes
| Issue Number | Issue Description | Severity |
|---|---|---|
| PB-4394 | KDMP restore failed when the snapshot size exceeded the PVC size. User Impact: Users experienced failures during KDMP restore for filesystem-based storage provisions when the PVC content was larger than the PVC size. Resolution: Modified the PVC size to match the snapshot size. Affected Versions: 24.3.1 and earlier |
Major |
| PB-8316 | Backups were incorrectly marked as successful, not partial, even when some volume backups failed. User Impact: Users were led to assume that all PVCs were successfully backed up, even when some had failed. Resolution: Updated the in-memory value of failedVolCount and the backup object to accurately reflect the number of failed backups.Affected Versions: 24.3.0 and 24.3.1 |
Major |
| PB-8360 | Addition of IBM COS backup location failed with an UnsupportedOperation error when the bucket was unlocked.User Impact: Users could not add an IBM COS backup location if it was unlocked. Resolution: The UnsupportedOperation error is now ignored for unlocked IBM COS buckets, indicating the bucket is not locked.Affected Versions: 24.3.1 |
Major |
| PB-7726 | VM Backup failed while executing auto exec rules if the virt-launcher pod of the VMs was not in a running state.User Impact: VM Backups failed when auto exec rules were applied. Resolution: Auto exec rules are now only executed on running virt-launcher pods.Affected Versions: 24.3.0 and 24.3.1 |
Major |
Known issues (Errata)
| Issue Number | Issue Description | Severity |
|---|---|---|
| PWX-38905 | If a StorageClass is deleted on the source and an asynchronous DR operation is performed for resources (PV/PVC) that use the deleted StorageClass, the migration fails with the following error:Error updating StorageClass on PV: StorageClass.storage.k8s.io <storageClassName> not foundWorkaround: You need to recreate the deleted StorageClass to proceed with the DR operation. Affected versions: 24.3.0, 24.3.1, and 24.3.2. |
Major |