-
Bug
-
Resolution: Done
-
Major
-
Pipelines 1.14.6, Pipelines 1.15.2
-
2
-
False
-
-
False
-
Chains Disabled status in TektonConfig no longer resets on Operator upgrade.
-
-
-
Pipelines Sprint Crookshank 21, Pipelines Sprint Crookshank 22
Description of problem:
chains config is disabled in tektonconfig, but it gets auto enabled when Pipelines operator is upgraded.
Before Upgrade:
chain: disabled: true options: disabled: false
After Upgrade:
chain: disabled: false options: disabled: false
Workaround
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
- Install OpenShift PIpelines operator and edit tektonconfig as below to disable chains config:
chain: disabled: true options: disabled: false
2. Upgrade the operator, and observe chains config is enabled again.
Actual results:
Chains config is re-enabled:
chain: disabled: false options: disabled: false
Expected results:
Chains config should remain disabled post operator upgrade.
Reproducibility (Always/Intermittent/Only Once):
Always
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):