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

ACM ignores Policies about empty label/field

XMLWordPrintable

    • 2
    • False
    • None
    • False
    • No
    • ?
    • GRC Sprint 2023-10, GRC Sprint 2023-11, GRC Sprint 2023-12, GRC Sprint 2023-13, GRC Sprint 2023-14, GRC Sprint 2023-15

      Description of problem:

      Wen create a policy to set some empty labels, like:

       

            - complianceType: musthave
                objectDefinition:
                  apiVersion: v1
                  kind: Node
                  metadata:
                    labels:
                      cluster.ocs.openshift.io/openshift-storage: ""               
                      node-role.kubernetes.io/worker: ""  
                      node-role.kubernetes.io/role2: ""
                    name: master-0

       

       

      This is ignored. It seems to be related to that empty label, that is used to add an extra role to a Node object.

      The policy appears as compliant, when it is not.

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

      2.7

      How reproducible:

      Create a policy that sets some empty fields, like a role for a Node.

      Steps to Reproduce:

      1.  
      2.  
      3. ...

      Actual results:

      The Policy appears as compliance. But this has not be applied, and the empty fields (roles) have not been added. You cannot enforce the Policy because it is set as compliance, when is not.

      Expected results:

      Additional info:

            rh-ee-jaszhang Jason Zhang
            jgato@redhat.com Jose Gato Luis
            Derek Ho Derek Ho
            Votes:
            2 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: