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

[2.7] Policy shows as "Compliant" despite there being violations

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • ACM 2.7.Z
    • ACM 2.6.4, ACM 2.7.2
    • GRC
    • None
    • 1
    • False
    • None
    • False
    • Important
    • +
    • No

      Description of problem:

      Customer has created a "Policy" with a "ConfigurationPolicy" that uses "complianceType: musthave" to ensure a LimitRange is always defined. "remediationAction: enforce" is set to make sure that the object is always applied.

      For most clusters, this works as expected. However the customer observed that RHACM reports that the Policy is showing "compliant: Compliant", when looking at certain objects directly, they can see that some objects are NOT compliant (despite the overall Policy being reported as "Compliant").

      This behaviour is visible in the following video: https://drive.google.com/file/d/12BVOeUYMYXFd4sVksnuSQuVGx0xexmbI/view

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

      • advanced-cluster-management.v2.6.4
      • OpenShift Container Platform 4.11.33

      How reproducible:

      Always at customer

      Steps to Reproduce:

      1. Create a "Policy" with a "ConfigurationPolicy" that uses "complianceType: musthave" to ensure a LimitRange object is always defined and apply it to multiple clusters
      2. Observe that the Policy reports as "Compliant"

      Actual results:

      Despite the Policy reporting as "Compliant", certain objects are showing violations

      Expected results:

      When a Policy reports as "Compliant", all objects are compliant and there are no violations when "remediationAction: enforce" is set.

      Additional info:

              mprahl Matthew Prahl
              rhn-support-skrenger Simon Krenger
              Derek Ho Derek Ho
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: