Description of Problem

• I try to create a new AppProject resource using YAML.  I want to apply specific permissions for groups as detailed in the documentation.  The groups in OpenShift are imported from LDAP and have long names - that is with the full DN.  When adding that LDAP group name the permissions are not applied.

Additional Info

• The OCP is air-gapped so I cannot extract logs etc.  

Problem Reproduction

• Create a group in OCP that has a long name.  I have not debugged to know whether it is because of the long group name (and LDAP is irrelevant) or because of the LDAP format
• You can see an example in the following YAML
  • app-project.yaml

Reproducibility

• Always

Prerequisites/Environment

• OpenShift, LDAP sync (maybe - it could be the length or the format of the group name and not LDAP)

Steps to Reproduce

• Explained above

Expected Results

• The group's permissions should be added

Actual Results

• No permissions are added

Problem Analysis

• <Completed by engineering team as part of the triage/refinement process>

Root Cause

• <What is the root cause of the problem? Or, why is it not a bug?>

Workaround (If Possible)

• <Are there any workarounds we can provide to the customers?>

Fix Approaches

• <If we decide to fix this bug, how will we do it?>

Acceptance Criteria

• ...

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Ensure code coverage is not reduced with the changes.
  • Integration tests have been automated.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested and merged on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written (if applicable).
• Build:
  • Code has been successfully built and integrated into the main repository / project.
  • Midstream changes (if applicable) are done, reviewed, approved and merged.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.