-
Bug
-
Resolution:
Unresolved
-
Normal
-
-
None
-
None
-
Description of Problem
- The value of`pod-security.kubernetes.io/enforce-version` label in openshift-gitops ns does not get reset upon changing the value
Additional Info
Problem Reproduction
- Install v1.14.2 from v1.15.0 catalog source
- Update the operator to v1.15
- Change the value of `pod-security.kubernetes.io/enforce-version` and save it
Reproducibility
Prerequisites/Environment
- OCP 4.17, GitOps candidate v1.15.0-7
Steps to Reproduce
- Refer to `Problem Reproduction`
Expected Results
- The value of the label gets reverted to the original
Actual Results
- Value of the label does not get reset
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.