Bug 2091003 - SSH service is not deleted along the VM
Summary: SSH service is not deleted along the VM
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.11.0
Assignee: Matan Schatzman
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-27 10:01 UTC by Guohua Ouyang
Modified: 2023-11-13 08:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-14 19:35:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt-ui kubevirt-plugin pull 521 0 None open Bug 2091003: Delete ssh service after vm delete 2022-05-31 10:54:51 UTC
Red Hat Issue Tracker CNV-18662 0 None None None 2023-11-13 08:16:39 UTC
Red Hat Product Errata RHSA-2022:6526 0 None None None 2022-09-14 19:35:14 UTC

Description Guohua Ouyang 2022-05-27 10:01:52 UTC 
Description of problem:
Have a VM with ssh enabled, check the ssh service is showing in networking service. Delete the VM, the ssh service is not deleted.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Guohua Ouyang 2022-06-09 01:39:15 UTC 
verified on OCP-v4.11.0-47
Comment 4 errata-xmlrpc 2022-09-14 19:35:03 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.11.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-2022:6526
Note You need to log in before you can comment on or make changes to this bug.