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:
When creating VM with 'URL/Download OS', there will be a status which is 'creating VM installation'. In this time, create a new VM with the same name and using 'Local Install Media' for its 'Installation Source', the old one will be covered

Version-Release number of selected component (if applicable):
cockpit-machines-208-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create a VM with 'URL/Download OS'
2. When the status of the VM is in 'creating VM installation', create another VM with the same name and using 'Local Install Media' for its 'Installation Source'

Actual results:
The information from the VM console prove the new VM covered the old one, and after a while, there will be an error which is " 'Couldn't create storage volume 'test-2.qcow2': 'storage volume 'test-2.qcow2' exists already' "

Expected results:
The VM should not be covered, and there should be an error which is like 'The VM already exists'

Additional info:

Fixed in https://github.com/cockpit-project/cockpit/pull/13298 , will be in 211.

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

Steps:
1. Create a VM with 'URL/Download OS'
2. When the status of the VM is in 'creating VM installation', create another VM with the same name and using 'Local Install Media' for its 'Installation Source'

There will be a prompt like "VM $name already exists"
So 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, 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