Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-8233

oc get policy still returns NonCompliant 10 minutes after deleting the certificate and secret

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • ACM 2.10.0
    • ACM 2.8.2
    • GRC
    • None
    • 2
    • False
    • None
    • False
    • GRC Sprint 2023-19, GRC Sprint 2023-20, GRC Sprint 2023-21, GRC Sprint 2023-22
    • Important
    • No

      Description of problem:

      oc get policy still returns NonCompliant 10 minutes after deleting the certificate and secret

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

      ocp 4.12.37
      advanced-cluster-management.v2.8.2

      multicluster-engine.v2.3.2

      How reproducible:

      ocp4.12.37
      1. install ACM and create mch
      2. install cert-manager operator
      3. create namespace
      4. create ManagedClusterSetBinding
      5. create Policy, Placement, and PlacementBinding
      6. check Policy state is 'Complaint'
      7. create Issuer and Certificate
      8. check Policy state is 'NonComplaint'
      9. delete Certificate and Secret
      10. check cert-policy-controller log "Found 0 non compliant certificates"
      11. check Policy state is 'NonComplaint' after several minutes
       

      Steps to Reproduce:

      1.  
      2.  
      3. ...

      Actual results:

      oc get policy still returns 'NonCompliant' 10 minutes after deleting the certificate and secret.

      Expected results:

      oc get policy returns 'Compliant' after deleting the certificate and secret after 30s.

      Additional info:

        1. log.txt
          6 kB
          Jun Wang
        2. must-gather-2023-10-18.tar.gz
          8.11 MB
          Jun Wang

              gparvin-redhat Gus Parvin
              wang.jun.1974 Jun Wang
              Derek Ho Derek Ho
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: