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

Configurations in tektonconfig is not persisting after operator upgrade

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • Pipelines 1.15.0
    • Pipelines 1.14.0, Pipelines 1.14.1
    • Operator
    • None
    • 3
    • False
    • None
    • False
    • Pipelines Sprint 261 TekShift

    Description

      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):

       

       *

      Attachments

        Issue Links

          Activity

            People

              jkandasa-rh Jeeva Kandasamy
              varadhya Veeresh Aradhya
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: