Bug 2188244

Summary:	[DPDK Checkup] Teardown does not happen on setup failure
Product:	Container Native Virtualization (CNV)	Reporter:	Orel Misan <omisan>
Component:	Networking	Assignee:	Orel Misan <omisan>
Status:	CLOSED ERRATA	QA Contact:	Yossi Segev <ysegev>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.13.0	CC:	phoracek
Target Milestone:	---
Target Release:	4.14.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	v4.14.0.rhel9-1123	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-08 14:05:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Orel Misan 2023-04-20 09:01:37 UTC

Description of problem:
Teardown does not happen in case of a setup failure.

The VMI and traffic generator pod will be garbage collected when the checkup Job will be deleted.

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


How reproducible:
100%


Steps to Reproduce:
1. Create a ConfigMap with a specification that will cause a setup failure, for example:
spec.param.trafficGeneratorNodeSelector: "node-that-does-not-exist"
2. Create the checkup job and link it to the ConfigMap from the previous step.

Actual results:
The setup will fail, but the teardown will not happen.


Expected results:
Teardown should happen - VMI and Pod should be removed.


Additional info:
In order to solve this bug, apply the following PR to the DPDK checkup:
https://github.com/kiagnose/kiagnose/pull/239

Comment 1 Yossi Segev 2023-10-12 13:54:53 UTC

Verified on
CNV 4.14.0
container-native-virtualization/kubevirt-dpdk-checkup-rhel9:v4.14.0-116

The complete teardown, including removal of the VMIs and pods, does happen eventually.
I opened a new BZ https://bugzilla.redhat.com/show_bug.cgi?id=2243672 in order to initiate the teardown immediately and not after the job timeout is reached.

Comment 3 errata-xmlrpc 2023-11-08 14:05:28 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Virtualization 4.14.0 Images security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:6817