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 checking 'Immediately Start VM', the vm will be created successfully and run correctly, but there is an error raised, which is 'Creation of VM ${vm_name} failed'

Version-Release number of selected component (if applicable):
cockpit-machines-197.1-1.el8.noarch
libvirt-dbus-1.2.0-2.module+el8.1.0+2983+b2ae9c0a.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Open the VM creation dialog
2. Connection: QEMU/KVM System connection
   Installation Source Type: URL
   Installation Source: url which is https and ostree
   Immediately Start VM: check

Actual results:
The vm runs correctly but there is an error which is 'Creation of VM ${vm_name} failed' raised.

Expected results:
The vm runs correctly and there is no error raised.

Additional info:
There is also a message shown on the console of browser:
The vm runs correctly but there is an error which is 'Creation of VM ${vm_name} failed' raised.

if set '--wait 0 --noreboot' for virt-install, $? in fedora is 0, in RHEL8 is 1

This looks like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1724287
I wonder why you see it though still, since virt-install 2.2.1 includes the fix and is in available in RHEL8.
Can you check the virt-install version in the machine that you verified this?

In addition since cockpit-199 we don't use wait=0, but this release is not available in RHEL8 indeed.

See:

commit 1d686a1ca44dffaf3261e90f85ce2035ae0a54ad
Author: Katerina Koukiou <kkoukiou>
Date:   Thu Jun 27 18:23:51 2019 +0200

    machines: bring back machine wait=-1 noreboot options on virt-install in the VM creation

Here is the version:
# rpm -qa | grep virt-manager
virt-manager-common-2.2.0-1.el8.noarch

So the bug is because of the lower version of virt-manager. It is also because of the old compose, the new version of virt-manager is not added. So should we just leave the bug here so that i can check it
in next compose?

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