Bug 2192938

Created attachment 1961992 [details]
screenshot.png

Description of problem (please be detailed as possible and provide log
snippests):
On a recently configured ACM and ODF Multicluster a customer attempted to implement the Regional DR. They have 2 managed cluster attached to ACM through submariner.
During the test They noticed that when they created a DRPolicy and wanted to apply it to an application that was created before that Policy or that was applied by another policy and now it's not, they cannot choose that application with the newly create DRPolicy.


Version of all relevant components (if applicable):
OCP 4.12
ACM 2.7

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
tech preview feature blocking tests of it

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

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


Can this issue reproducible?
customer environment

Can this issue reproduce from the UI?
yes

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


Steps to Reproduce:
1 - install and configure ACM and ODF multicluster to implement regional DR
2 - attach two clusters to ACM using submariner
3 - create an application app1
4 - Apply policyA to app1
5 - delete policyA
6 - Create DRPolicy policyB



Actual results:
unable to apply policyB to app1

Expected results:
able to apply policyB to app1

Additional info:
- screenshot uploaded
- If they create an ACM application "standalone" (so it's not managed by the ACM main application), they are able to create and apply a DRPolicy.
- If they create an ACM application "managed" (so it's under the ACM main application), they are able to create the DRPolicy, but are not able to apply it. 
- The web console's prompt does not even see it as an application, in fact it does not even see any application of the managed ones.
- They also noticed that they are able to create a DRPlacementControl, successfully, in order to link the managed application and the DRPolicy, but we are not able to execute a failover or a relocate and from the ACM web console -> DataServices ->Data Policies the said DRpolicy does not appear to be linked to any application (even if we create the DRPlacementControl)
- They configured ACM on the Hub Cluster and a GitHub organisation. Inside this organisation we create an "infra repository" in which we have the following structure:
~~~
- main-subscription
   - YAML resources (1 application, 1 sub, 1 channel, 1 namespace, 1 placement rule)
- managed-subscriptions
   - subfolder1
      - YAML resources (1 application, 1 sub, 1 channel, 1 namespace, 1 placement rule)
   - subfolder2
      - YAML resources (1 application, 1 sub, 1 channel, 1 namespace, 1 placement rule)
~~~
each ACM application correspond to a namespace (1 ACM application = 1 namespace) and these applications are managed by a main ACM application. The "managed" applications point to other repositories inside the organisation and each of these repositories correspond to a namespace (1 ACM managed application = 1 namespace = 1 repository). Inside there are various folders where each folder contains the YAML resources that describe a workload (a deployment, a service, a pvc ....).