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

Handle naming conflict with gatekeeper constraints and templates

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • ACM 2.9.0
    • None
    • GRC
    • None
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • GRC Sprint 2023-16, GRC Sprint 2023-17, GRC Sprint 2023-18
    • Moderate
    • No

      Description of problem:

      We have code that does not allow two config policies to have the same name.  You can't have gatekeeper constraints with the same name either.  Same for constrainttemplates.  You can have a constraint and constraint template that have the same name.  In that case the status is being returned, but it's not correct.

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

      How reproducible:

      I think it is easily reproducible.  There may be some randomness in how the status is returned.

      Steps to Reproduce:

      1. Create policy with gatekeeper constraint and constrainttemplate that have a common name
      2. The policy status won't work properly
      3. ...

      Actual results:

      Expected results:

      Additional info:

              gparvin-redhat Gus Parvin
              gparvin-redhat Gus Parvin
              Derek Ho Derek Ho
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: