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 2155762 - On deleting of a Pipeline run, child objects are not cleaned up
Summary: On deleting of a Pipeline run, child objects are not cleaned up
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Infrastructure
Version: 4.11.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: future
Assignee: Karel Šimon
QA Contact: Geetika Kapoor
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-22 09:35 UTC by Dominik Holler
Modified: 2023-12-14 16:06 UTC (History)
1 user (show)

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

Attachments (Terms of Use)


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

Description Dominik Holler 2022-12-22 09:35:32 UTC 
Description of problem: If an active pipeline run is deleted, the created VM is not deleted.


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


How reproducible:


Steps to Reproduce:
1. Trigger the windows10-installer pipeline with an invalid url for the windows iso
2. Wait until the VM is created in wait-for-vmi-status
3. Delete the pipeline run 


Actual results: The temporary VM still exists.


Expected results: All objects created by the pipeline run are cleaned up, including the temporary VM


Additional info: Maybe an ownerReference to the PipelineRun, so that k8s cleans the VM and DV after failure.
Note You need to log in before you can comment on or make changes to this bug.