Skip to content

v24.3.3

Latest
Compare
Choose a tag to compare
@cnbu-jenkins cnbu-jenkins released this 22 Nov 04:46

Fixes

Issue Number Issue Description Severity
PB-8394 If a smaller pxd volume of a few MB and a larger volume of, let's say, 500 GB, are backed up, the status of the smaller backup throws a false error: Backup failed for volume: rpc error: code = Internal desc = Failed to get status of backup: Key not found.

User Impact: The backup appears to be in a failed state with the key not found error, but the backup was actually successful and uploaded to the cloud.

Resolution: Once the backup reaches a successful state, we stop checking its status.

Affected Versions: 24.3.2 and earlier
Minor
PB-7944 For large resources, the resources are fetched twice, increasing the backup completion time.

User Impact: Large resource backups take longer to complete.

Resolution: Resources are now fetched only once and uploaded in the same reconciler context. Note: This fix is applicable only for S3 object store.

Affected Versions: 24.3.2 and earlier
Minor
PB-7476 Node affinity was not set up in the kopia/NFS backup and restore job pods, allowing these job pods to be scheduled on nodes where the applications to be backed up were not running. This led to backup failures.

User Impact: If there are network restrictions on certain nodes and applications are not running on those nodes, there's a risk that the backup job pods may get scheduled on these restricted nodes, causing the backup to fail.

Resolution: Added node affinity for the job pods to ensure they are scheduled on the desired nodes where the application pods are running.

Affected Versions: 24.3.2 and earlier
Minor

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 found

Workaround: You need to recreate the deleted StorageClass to proceed with the DR operation.

Affected versions: 24.3.0, 24.3.1, 24.3.2, and 24.3.3
Major