Bug 2045115

Summary:	Some objects (I.E. SSH Service) are not removed when VM is deleted.
Product:	Container Native Virtualization (CNV)	Reporter:	pmoses
Component:	Virtualization	Assignee:	sgott
Status:	CLOSED DUPLICATE	QA Contact:	Kedar Bidarkar <kbidarka>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.8.0	CC:	cnv-qe-bugs, fdeutsch, sgott, stirabos, tnisan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-02-02 12:45:19 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 pmoses 2022-01-25 15:49:47 UTC

Description of problem:
SSH service is not removed when VM is deleted 

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


How reproducible:
100%

Steps to Reproduce:
1. Create VM
2. Expose SSH via node port
3. Delete VM

Actual results:
exposed SSH service via node port remains

Expected results:
All objects from the deleted VM are removed

Additional info:

Comment 1 Simone Tiraboschi 2022-01-26 14:47:38 UTC

Moving to virt component

Comment 2 sgott 2022-01-26 15:47:05 UTC

Was this VM created using the UI or via command line?

Assuming you used the web interface, I believe this might be a UI issue, since that's where the service object was created. Please feel free to re-assign if you think this is not the correct component.

I wonder, if the service was created with an ownerReference linked to the VM, would a cascading deletion then happen automatically?

Comment 3 sgott 2022-01-26 15:48:40 UTC

BZ was moved in error. Confirmation of the reporter's workflow is in order in order to understand where the problem lies. Moving back to virt for now.

Comment 4 Tal Nisan 2022-01-26 17:04:38 UTC

It seems to me that this is the same as bug 2019494, in that case it is fixed in 4.9.z

Comment 5 Fabian Deutsch 2022-02-02 12:45:19 UTC

Closing this as a dupe

*** This bug has been marked as a duplicate of bug 2019494 ***