-
Bug
-
Resolution: Done
-
Normal
-
4.12.z
-
Low
-
None
-
X-Files 232
-
1
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-5466. The following is the description of the original issue:
—
Description of problem:
It is possible to change some of the fields in default catalogSource specs and the Marketplace Operator will not revert the changes
Version-Release number of selected component (if applicable):
4.13.0 and back
How reproducible:
Always
Steps to Reproduce:
1. Create a 4.13.0 OpenShift cluster 2. Set the redhat-operator catalogSource.spec.grpcPodConfig.SecurityContextConfig field to `legacy`.
Actual results:
The field remains set to `legacy` mode.
Expected results:
The field is reverted to `restricted` mode.
Additional info:
This code needs to be updated to account for new fields in the catalogSource spec.
- clones
-
OCPBUGS-5466 Default CatalogSource aren't always reverted to default settings
- Closed
- is blocked by
-
OCPBUGS-5466 Default CatalogSource aren't always reverted to default settings
- Closed
- links to
(3 links to)