-
Bug
-
Resolution: Done
-
Critical
-
Pipelines 1.14.0, Pipelines 1.14.1
-
None
-
3
-
False
-
None
-
False
-
-
-
Pipelines Sprint TekShift 1
Description of problem:
Configurations in tektonconfig is not persisting after operator upgrade.
This issue was observed in our CI cluster, where we had set the enable-api-fields as alpha and after the upgrade of the operator from 1.13.1 to 1.14.0 (1.14.0 to 1.14.1), the tektonconfig contained enable-api-fields as alpha but the key enable-api-fields was not present in the feature-flags configmap in openshift-pipelines namespace
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
I could not reproduce the issue in a test cluster.
Actual results:
The configurations in tektonconfig is not persisting after the operator upgrade
Expected results:
The configurations in tektonconfig should persist even after operator upgrade
Reproducibility (Always/Intermittent/Only Once):
Only Once
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):
*
- duplicates
-
SRVKP-4159 "options" adding resource entries on multiple installersets
- Verified
- is related to
-
SRVKP-4159 "options" adding resource entries on multiple installersets
- Verified