Bug 2039378

Summary: Deploying CRD via Application does not update status in ACM console
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Sam Scarpello <sam.scarpello>
Component: ConsoleAssignee: Kevin Cormier <kcormier>
Status: CLOSED ERRATA QA Contact: Ruici Hong <ruhong>
Severity: high Docs Contact: Christopher Dawson <cdawson>
Priority: unspecified    
Version: rhacm-2.4CC: dho, dhuynh, huichen, jpateteg, juhsu, rislam
Target Milestone: ---Flags: ruhong: qe_test_coverage+
juhsu: rhacm-2.4.z+
Target Release: rhacm-2.4.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-03 07:00:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
CRD status does not update, even after successfully deploying. none

Description Sam Scarpello 2022-01-11 15:57:27 UTC 
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.
Comment 1 bot-tracker-sync 2022-01-14 22:10:54 UTC 
G2Bsync 1013460767 comment 
 chenz4027 Fri, 14 Jan 2022 20:43:20 UTC 
 G2Bsync release 2.4.2 will contain the fix.
Comment 2 Ruici Hong 2022-02-07 21:32:17 UTC 
Waiting for 2.4.2-rc3 to verifiy
Comment 3 Ruici Hong 2022-02-15 15:45:28 UTC 
Tested and verified on cluster `alc-auto`
ACM - `2.4.2-RC3`
OCP - `4.8.2`

![image](https://user-images.githubusercontent.com/83980331/154096729-afe905d1-c68c-4034-9af4-ac7c3c8c9058.png)
Comment 4 Ruici Hong 2022-02-15 15:53:29 UTC 
https://polarion.engineering.redhat.com/polarion/#/project/RHACM4K/workitem?id=RHACM4K-10668
test case added
Comment 9 errata-xmlrpc 2022-03-03 07:00:23 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Red Hat Advanced Cluster Management 2.4.2 security updates and bug fixes), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:0735