Description of problem: 

The ACM topology view does not show the correct status when the subscription namespace differs from the resource namespace. In the diagram, the Deployment, ReplicationSet, and the pod are shown with unknown status, but everything is deployed correctly on the managed cluster.

See attached image

Notice: This is a UI issue; the deployment is successful. 

Version-Release number of selected component (if applicable):

2.9.2

2.7.4

This works properly in 2.4.2

How reproducible:

100%

Steps to Reproduce:

1. https://github.com/senthilredhat/acm-config-maint-groups/tree/acm-policies

1. This git repo deploys the subscription to a different namespace (dev-primary) and the application manifests are deployed to a different namespace (hello-world)
2. Steps to deploy the repo
   1. Create a secret acm-config-maint-groups-secret for the repo
   2. Install Channel oc apply -k init\channel
   3. install sub-of-sub oc apply -k init\subscription-of-subscriptions
   4. You need to have a cluster with labels env=dev & fault-domain=primary

Actual results:

The UI reports the the resources are in an unknown state

Expected results:

The UI reports the correct status

Additional info:

Our customer needs this fix to be back ported to 2.7.4