Description of problem (please be detailed as possible and provide log
snippests):

Testing replace cluster with Subscription and Application set type Worklaod using below doc on ODF 4.16

https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.16/html-single/configuring_openshift_data_foundation_disaster_recovery_for_openshift_workloads/index?extIdCarryOver=true&sc_cid=701f2000001Css5AAC#recovering-to-a-replacement-cluster-with-mdr_manage-mdr

At step 12 in above doc(after reconfiguring DR) When I Applied drpolicy to subscription type workload VRG is not created in sub wl namespace rather it gets created in ApplicationSet type Workload namespace.

Note: Both type of Workloads has cephfs pvc and rbd pvc in same namespace.

Sub Worklaod- https://github.com/red-hat-storage/ocs-workloads/tree/master/mdr/subscriptions/busybox-app-1
Appsey Workload - https://github.com/red-hat-storage/ocs-workloads/blob/master/mdr/AppSet/appset-busybox-1

Status After applying DRpolicy to sub Workload:
-----------------------------------------------

➜ hub oc get drpc -A
NAMESPACE NAME AGE PREFERREDCLUSTER FAILOVERCLUSTER DESIREDSTATE CURRENTSTATE
busybox-workloads-1 busybox-1-placement-drpc 74m asagare-sc1 Deployed

Subscription:
==============
➜ clust2 oc get pods,pvc,vr,vrg -n busybox-workloads-1
NAME READY STATUS RESTARTS AGE
pod/busybox-cephfs-pod-1-658f6b7fd5-qq8dl 1/1 Running 0 109m
pod/busybox-rbd-pod-1-7f4d7cc6c7-fdlmw 1/1 Running 0 109m

NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS VOLUMEATTRIBUTESCLASS AGE
persistentvolumeclaim/busybox-cephfs-pvc-1 Bound pvc-bac0af11-0dc5-416b-b630-365343a64db1 100Gi RWO ocs-external-storagecluster-cephfs <unset> 110m
persistentvolumeclaim/busybox-rbd-pvc-1 Bound pvc-6d13fec7-0729-4593-9db2-2614758dd41c 100Gi RWO ocs-external-storagecluster-ceph-rbd <unset> 110m

➜ oc get vr,vrg -A
NAMESPACE NAME DESIREDSTATE CURRENTSTATE
appset-busybox-1 volumereplicationgroup.ramendr.openshift.io/busybox-1-placement-drpc primary Primary

ApplicationSet:
===============
oc get pods,pvc,vr,vrg -n appset-busybox-1
NAME READY STATUS RESTARTS AGE
pod/busybox-cephfs-pod-1-658f6b7fd5-bbqqv 1/1 Running 0 104m
pod/busybox-rbd-pod-1-7f4d7cc6c7-x5q99 1/1 Running 0 104m

NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS VOLUMEATTRIBUTESCLASS AGE
persistentvolumeclaim/busybox-cephfs-pvc-1 Bound pvc-43c65b8e-326c-4055-8727-c44c0d83ab3e 100Gi RWO ocs-external-storagecluster-cephfs <unset> 107m
persistentvolumeclaim/busybox-rbd-pvc-1 Bound pvc-8b9a5bdd-849a-4d38-b269-399433ef7fda 100Gi RWO ocs-external-storagecluster-ceph-rbd <unset> 107m

NAME DESIREDSTATE CURRENTSTATE
volumereplicationgroup.ramendr.openshift.io/busybox-1-placement-drpc primary Primary

Version of all relevant components (if applicable):

OCP: 4.16.0-0.nightly-2024-09-03-161040
ODF: 4.16.2-3
ACM: 2.11.3
CEPH:18.2.1-229.el9cp (ef652b206f2487adfc86613646a4cac946f6b4e0) reef (stable)

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes

Is there any workaround available to the best of your knowledge?
NA

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

1

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
Yes

If this is a regression, please provide more details to justify this:

Steps to Reproduce:
1.Deploy MDR environment
2. Deploy Subscription and ApplicationSet type Workload
3.Followed Steps from below document document-

https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.16/html-single/configuring_openshift_data_foundation_disaster_recovery_for_openshift_workloads/index?extIdCarryOver=true&sc_cid=701f2000001Css5AAC#recovering-to-a-replacement-cluster-with-mdr_manage-mdr

Actual results:
VRG is creating in Application set Workload namespace

Expected results:
VRG should gets created in Subscription type workload namespace

Additional info: