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.