Bug 2143439

Description of problem (please be detailed as possible and provide log
snippests):
Using new 'Failover' and 'Relocate' UI in the Application dropdown in 'All Clusters' seems to not be working as expected. After a manual Failover (edited DRPC to action=Failover with failoverCluster=cluster2) it was not possible to 'Relocate' back to the preferred Cluster (cluster1) using the UI. I had to 'Relocate' to the failoverCluster (cluster2) and 'Initiate' change so the preferred and failover cluster were the same. Subsequent UI action of 'Relocate' worked using preferredCluster (cluster1).

Version of all relevant components (if applicable):
$ oc version
Client Version: 4.12.0-rc.0
Kustomize Version: v4.5.7
Server Version: 4.12.0-rc.0
Kubernetes Version: v1.25.2+f33d98e

Managed clusters:
$ oc get csv -n openshift-storage
NAME                                         DISPLAY                         VERSION             REPLACES   PHASE
mcg-operator.v4.12.0-111.stable              NooBaa Operator                 4.12.0-111.stable              Succeeded
ocs-operator.v4.12.0-111.stable              OpenShift Container Storage     4.12.0-111.stable              Succeeded
odf-csi-addons-operator.v4.12.0-111.stable   CSI Addons                      4.12.0-111.stable              Succeeded
odf-operator.v4.12.0-111.stable              OpenShift Data Foundation       4.12.0-111.stable              Succeeded
odr-cluster-operator.v4.12.0-111.stable      Openshift DR Cluster Operator   4.12.0-111.stable              Succeeded

Hub cluster:
$ oc get csv -n openshift-operators
NAME                                               DISPLAY                         VERSION             REPLACES   PHASE
odf-multicluster-orchestrator.v4.12.0-111.stable   ODF Multicluster Orchestrator   4.12.0-111.stable              Succeeded
odr-hub-operator.v4.12.0-111.stable                Openshift DR Hub Operator       4.12.0-111.stable              Succeeded

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, if using UI for Failover and Relocate

Is there any workaround available to the best of your knowledge?
Yes, Relocate to the failoverCluster which makes preferedCluster=failoverCluster

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
Yes


Steps to Reproduce:
1.Configure RDR test environment with OCP/ODF 4.12
2.Create DRPolicy via "All Cluster" UI
3.Deploy application and apply DRPolicy via UI
4.Using CLI method modify DRPC and add action=Failover and failoverCluster=<clustername2>
5.Wait for Failover to get to Completed and then navigate on hub cluster "All Clusters" to Applications-><application> and use dropdown to select 'Relocate' and select 'Target' <clustername1>.


Actual results:
Selecting the 'Target' to be <clustername1> in UI leaves other settings greyed out including 'Initiate'.

Expected results:
Selecting the 'Target' to be <clustername1> in UI has other setting actionable and 'Initiate' can be selected.

Additional info: