Bug 2063862

Summary:	S3 validation failure on the failed cluster prevents failover for Metro DR
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Raghavendra Talur <rtalur>
Component:	odf-dr	Assignee:	Raghavendra Talur <rtalur>
odf-dr sub component:	ramen	QA Contact:	Martin Bukatovic <mbukatov>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	kramdoss, kseeger, madam, mbukatov, mmuench, muagarwa, nberry, ocs-bugs, odf-bz-bot, rperiyas, srangana
Version:	4.10
Target Milestone:	---
Target Release:	ODF 4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.10.0-210	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-21 09:12:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Raghavendra Talur 2022-03-14 14:12:23 UTC

Description of problem (please be detailed as possible and provide log
snippests):
When the primary cluster fails in a Metro DR configuration, the S3 store may also be down. In that scenario, the s3 validation code in Ramen prevents the failover process from progressing.


Version of all relevant components (if applicable):
4.10


Is there any workaround available to the best of your knowledge?
No workarounds.

Can this issue reproducible?
Yes. If the S3 store is cohosted with ODF. Like it is in the default ODF setup.

Steps to Reproduce:
1. Setup Metro DR with S3 store on both the Metro DR clusters and provide them in the Ramen config.
2. Bring down the primary cluster and initiate the failover process by editing the fencing status for the failed cluster.


Actual results:
The failover process is stuck.

Expected results:
The failover process should complete.

Comment 5 Raghavendra Talur 2022-03-16 14:53:01 UTC

Patch posted upstream at https://github.com/RamenDR/ramen/pull/405