Known Issues in DataCore Puls8 v4.4

This section documents the known issues that may impact this release, including any available workarounds or mitigation steps.

The items below describe the known issues:

Kernel Crash on Oracle Linux 9 During NVMe-TCP Volume Detach Operations (CVE-2024-53170)

When running Replicated PV Mayastor on Oracle Linux 9 (kernel 5.14.x), servers may unexpectedly reboot during volume detach operations due to a kernel bug (CVE-2024-53170) in the block layer. This issue is not caused by Replicated PV Mayastor but is triggered more frequently because of its NVMe-TCP connection lifecycle.

Workaround: Upgrade to kernel 6.11.11, 6.12.2, or later, which includes the fix.

Velero Uninstall Removes DataCore Puls8 Namespace and Components

When Velero is enabled via kubectl puls8, using the velero uninstall -n puls8 command is not recommended. This command attempts to delete the entire Puls8 namespace, expecting it to be used exclusively by Velero, and removes all Puls8 components.

Workaround: Instead of using the Velero CLI uninstall command, run the following command to safely remove only Velero-specific components:

kubectl puls8 velero uninstall --release-name puls8 --chart-name oci://registry-1.docker.io/datacoresoftware/puls8 -n puls8

Backup Hangs When Namespace Contains Replicated Volumes and Local Volumes

When backing up a namespace with a mix of Replicated PV Mayastor and Local PV Hostpath / Local PV LVM volumes, the Velero backup job includes all PVCs. Since Local PV LVM does not support CSI snapshot restore end-to-end, the backup may remain in the WaitForPluginAction state.

Workaround: Avoid creating Local PV Hostpath / Local PV LVM PVCs in the same namespace as Replicated PV Mayastor volumes. Alternatively, use a label selector during backup (Example: --selector backup=true) to limit the backup to specific resources.

Block-Mode Snapshot Export Limitation

There is a known limitation when using Veeam Kasten backups with Replicated PV Mayastor volumes in block mode. Snapshot export operations may fail.

Workaround: Use filesystem mode PVCs instead of block mode and ensure that the VolumeSnapshotClass and CSI driver capabilities are properly configured before initiating backups.