Bug 2121417

Summary:	[RDR] Relocate Operation of workload starts even when ClusterDataProtected is false
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Shyamsundar <srangana>
Component:	odf-dr	Assignee:	Shyamsundar <srangana>
odf-dr sub component:	ramen	QA Contact:	krishnaram Karthick <kramdoss>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	madam, muagarwa, ocs-bugs, odf-bz-bot
Version:	4.12
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-10-05 18:17:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Shyamsundar 2022-08-25 12:22:52 UTC

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

Comment 2 Shyamsundar 2022-10-05 18:17:45 UTC

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.