Created attachment 1850130 [details]
CRD status does not update, even after successfully deploying.

Description of problem:

After deploying software with ACM to managed clusters (installing Kyverno software in this case), CRD objects show as "Not Deployed" in ACM web console, even though the deployment seems to have succeeded.  Using an Application/Subscription object to deploy, and source is in a local enterprise github instance.

I only see this on CRD objects (CustomResourceDefinition), and this persists after applying Subscription-admin, as per 
   https://access.redhat.com/solutions/6010251 
using the policy at 
   https://github.com/open-cluster-management/policy-collection/blob/main/community/CM-Configuration-Management/policy-configure-subscription-admin-hub.yaml

I can recreate this problem with any CRD, there does not appear to be anything special about the CRDs I am deploying.  Should be very easy to replicate.


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

How reproducible:
Deploy an Application to a managed cluster, make sure this application includes a CRD (CustomResourceDefinition).  Since a CRD is not contained in the subscription namespace, you have to apply subscription-admin role as per https://access.redhat.com/solutions/6010251

Actual results:
CRD objects in ACM web console remain with status "Not Deployed"

Expected results:
CRD objects, once deployed, should show correct status.