This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2155088 - tekton pipelineruns are getting stuck if stopped in middle of taskruns
Summary: tekton pipelineruns are getting stuck if stopped in middle of taskruns
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Infrastructure
Version: 4.12.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: future
Assignee: Karel Šimon
QA Contact: Geetika Kapoor
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-19 23:18 UTC by Geetika Kapoor
Modified: 2023-12-14 16:06 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-12-14 16:06:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   CNV-23480 0 None None None 2023-12-14 16:06:05 UTC

Description Geetika Kapoor 2022-12-19 23:18:56 UTC
Description of problem:
tekton pipelineruns are getting stuck if stopped in middle of taskruns (example: wait-for-vmi-status). This will show that piperuns are getting cancelled but even after 15 mins they are not cancelled.All the resouces are in stuck mode.

 oc get pipelineruns -A -w
NAMESPACE       NAME             SUCCEEDED   REASON                  STARTTIME   COMPLETIONTIME
openshift-cnv   test-io-ing-yu   Unknown     StoppedRunningFinally   32m  

When pipelines are deleted in middle of taskruns we see leftovers like vm,vmi.

Version-Release number of selected component (if applicable):
4.12

How reproducible:
always when we tried to interrupt a taskrun

Steps to Reproduce:
1.when vmi task starts , perform a stop operation and pipelines get stuck.
2.
3.

Actual results:


Expected results:


Additional info:

For all kind of operation that we perform 'type' is always succeeded. is it right information?

{'lastTransitionTime': '2022-12-19T22:40:43Z',
 'message': 'Tasks Completed: 1 (Failed: 0, Cancelled 0), Incomplete: 6, '
            'Skipped: 0',
 'reason': 'Running',
 'status': 'Unknown',
 'type': 'Succeeded'}


Note You need to log in before you can comment on or make changes to this bug.