Description of problem: By default, deleting a running vm results in the deletion of the vm and the associated vmi. When `--cascade=orphan` is used, it should result in the deletion of the vm, but the associated vmi should be left running. Version-Release number of selected component (if applicable): 4.1.13 How reproducible: 100% Steps to Reproduce: 1. Create a vm and start it 2. Delete the vm with `kubectl delete vm <vm_name> --cascade=orphan` 3. Actual results: The vmi disappears Expected results: The vmi should not be deleted Additional info:
verify with build: CNV-v4.13.0.rhel9-1639 step: 1: create a vm and start it $ oc get vm NAME AGE STATUS READY vm-fedora 12m Running True 2: Delete the vm with `kubectl delete vm <vm_name> --cascade=orphan` $ kubectl delete vm vm-fedora --cascade=orphan virtualmachine.kubevirt.io "vm-fedora" deleted $ oc get vmi NAME AGE PHASE IP NODENAME READY vm-fedora 12m Running 10.129.2.155 c01-zpeng-413-sv526-worker-0-8dp6m True try to connect vmi with console, it worked. move to verified.
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 (Moderate: OpenShift Virtualization 4.13.0 Images security, bug fix, and enhancement 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:3205