Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-8621

tektonpruner configmap values are getting overrided after upgrade

XMLWordPrintable

      Description of problem:

      tektonpruner configmap values are getting overrided after upgrade

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      1. Install 1.19.3 operator 
      2. Enable tektonpruner & update tekton-pruner-default-spec configmap with some values.
      global-config: |-    
          enforcedConfigLevel: global
          historyLimit: 8
          failedHistoryLimit: 3
          successfulHistoryLimit: 5  
      1. Create few pipelineruns in test namespaces and validate pipelineruns are being pruned with the values set in configmap.
      2. Upgrade the operator to 1.20
      3. Once the operator upgrade is done, validate the values of tekton-pruner-default-spec configmap.

      Actual results:

      tekton-pruner-default-spec configmap values are getting overrided with default values as below.

      global-config: |
          enforcedConfigLevel: global
          ttlSecondsAfterFinished: null
          successfulHistoryLimit: null
          failedHistoryLimit: null
          historyLimit: 100
          namespaces: {} 

      Expected results:
      The same data before upgrade should be retained in configmap even after upgrade

       

      Reproducibility (Always/Intermittent/Only Once):

      Acceptance criteria: 

       

      Definition of Done:

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

      1.19.3_config_beforeupgrade.yaml

       *

              rh-ee-prbindal Pramod Bindal
              rh-ee-smanthin Sai Raju Manthina
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: