This bug was initially created as a copy of Bug #2121159 I am copying this bug because: The original BZ detailed a stuck relocation operation due to ClusterDataReady being false. Ramen should not start the relocation if ClusterDataReady is false, as this implies the workload is not fully healthy for relocation. This BZ is hence to track changes to ensure the above before starting relocation, and also to possibly add the following condition to Ramen: - Add a "Healthy" condition that summarizes the current workload health as true/false with appropriate reasons
Closing the BZ for the following reasons: - DRPC already checks for DataReady, which is set to false till PVCs are created - ClusterDataReady is a pre-condition for app/PVC deployment, hence any PVC that is deployed needs to meet DataReady for relocation IOW, ClusterDataReady as a pre-check for readiness to relocate is not required.