VM recipe known issues
Lists known VM recipe issues.
ramendr.openshift.io/k8s-resource-selector label is not automatically
applied when a PVC is added to an already protected workload NS
- Problem
-
When an additional PV or PVC is attached to an already protected VM on Day 2, the newly created PV/PVC is not automatically protected.
- Resolution
-
To ensure the new PV/PVC is protected, manually add the following label on the new PV/PVC:
("ramendr.openshift.io/k8s-resource-selector": "<value same as that of base PVC of associated VM>")This label links the new PV/PVC to the existing protected group of resources.
DRPolicy without flattening applied to a cloned volume leads to errors
- Problem
-
Regional-DR currently does not support volumes created from CSI snapshots or clones in protected applications. These volumes rely on a parent volume that isn’t replicated.
- Resolution
-
To avoid these issues, use a DRPolicy that flattens PVs before replication if cloning is required.
For more information, see this knowledgebase article.