-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
-
False
Description of problem:
When a Pipelines component uses finalizers (e.g. Chains or Results) and is disabled in the TektonConfig, all PipelineRuns which have not yet been deleted still have the component's finalizer. This prevents those pipelineruns from being deleted without manual intervention.
Workaround
The only workaround is use a kubectl patch to remove all finalizers from the effected pipelineruns.
Prerequisites (if any, like setup, operators/versions):
Start a cluster with Openshift Pipelines and Tekton Results or Chains
Steps to Reproduce
- Start a number of PipelineRuns which take a while, e.g. with Tasks that just sleep for 30 minutes
- In the TektonConfig, disable Results or Chains
- Once the pipelineruns complete, delete them using kubectl
Actual results:
The pipelineruns all remain in the cluster in a "deleting" state and the Results or Chains finalizers
Expected results:
The pipelineruns are deleted from the cluster.
Reproducibility (Always/Intermittent/Only Once):
Always
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):
*
- links to