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

"The operator pod is failing with a "panic: runtime error: invalid memory address or nil pointer dereference" error after the OpenShift Pipelines 1.19.0 upgrade."

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • Pipelines 1.19.3
    • Pipelines 1.19.0
    • Operator, QA
    • None
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • Fixes a crash in the OpenShift Pipelines Operator pod while upgrading to version 1.19.0 caused by a nil pointer reference at startup if tektonconfig`s `spec.tektonpruner.disabled` is `nil`
    • Bug Fix
    • Proposed
    • Hide

      This issue is applicable for v1.19.0 & v1.19.1 only. The patch fix for this issue is shipped in v1.19.2. Immediate workaround would be to set the tektonconfig's `spec.tektonrpuner.disabled` to `true`

      Show
      This issue is applicable for v1.19.0 & v1.19.1 only. The patch fix for this issue is shipped in v1.19.2. Immediate workaround would be to set the tektonconfig's `spec.tektonrpuner.disabled` to `true`

      Description of problem:

      After upgrading to OpebnShift Pipelines 1.19.0, operator pod is crashing with error panic: runtime error: invalid memory address or nil pointer dereference

      2025-07-29T18:15:28.854224612Z panic: runtime error: invalid memory address or nil pointer dereference
2025-07-29T18:15:28.854231250Z [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x203748b]

      Additional info:

      Upstream PR > https://github.com/tektoncd/operator/pull/2810

      This issue is observed when `.spec.tektonpruner.disabled` is set to `null` in TektonConfig `config` CR as shown below :

      ~~~
      tektonpruner:
      disabled: null <---------
      options: {}
      ~~~

              rh-ee-anataraj Anitha Natarajan
              rhn-support-dkarde Dipak Karde
              Sri Vignesh Selvan Sri Vignesh Selvan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: