RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
If delete a VM whose installation source type is 'URL' or 'PXE', the VM state which is shown on the page will become 'in transition'. Then check the VM by using 'virsh list --all', the VM is not in the result of the command.But the VM should disappear form page this time.

Version-Release number of selected component (if applicable):
cockpit-machines-197.2-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+3531+2918145b.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create a VM whose installation source type is 'URL' or 'PXE', then click 'Install' button of it
2. Click the 'Delete' button of the VM

Actual results:
On the page, the state of the VM will become 'in tansition' , then check the VM by using 'virsh list --all', the VM is not in the result of the command.

Expected results:
The VM will disappear from page, then check the VM by using 'virsh list --all', the VM is not in the result of the command.

Additional info:
The VM whose state is 'in transition' will disappear after refresh the page.

This was fixed with:
commit 9b3927ab0b14ea975c759cc4979a9e0967c77eea
Author: Katerina Koukiou <kkoukiou>
Date:   Thu Jun 27 21:56:13 2019 +0200

    machines: don't redefine the domain when user deletes it in the middle of the installation

$ git describe 9b3927ab0b 
198-49-g9b3927ab0


The above commit is not inside of cockpit-197 thus you are seeing this issue there.

Verified with packages:
cockpit-machines-208-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64

Steps:
1. Create a VM with installation source : 'URL' or 'PXE', then click 'Create' 
2. Wait until console shows up ,the Click the 'Delete' button of the VM
3. Check on host by:
# virsh list --all

The VM can be deleted successfully in step 2.
The VM is not in the result of the command in step 3.

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, 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/RHBA-2020:1639