Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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 shutdown the guest and start to clone the guest quickly,
the dialog will close immediately without error.
Version-Release number of selected component (if applicable):
virt-manager-0.9.0-28.el6.x86_64
libvirt-0.10.2-46.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Prepare a guest and open clone dialog
# virt-manager
Right click on the guest and choose clone to open clone dialog
2. Right click again on the guest, and click run, to start the guest
3. Right click on the guest, choose "Shut down" and click "Force off"
The confirm dialog will comes out, click yes button and do step4 quickly.
4. After step 3, must click clone button on the clone dialog quickly
(This operation should be very quick, you can put the force off confirm dialog near the clone dialog, so can click clone button after click yes quickly)
Actual results:
Step 4, the clone dialog will close immediately.
Try to start the guest, with error:
Error starting domain: Cannot start
guest while cloning operation in progress.
In the guest list, there is no new guest be cloned.
In the image dir, there is no new image be cloned.
Expected results:
Should not close the dialog and should clone a new guest successfully.
Additional info:
If I restart libvirtd, the guest can start normally.
And the guest can start on another host with remote connection of virt-manager.
Comment 2Giuseppe Scrivano
2014-09-22 11:33:27 UTC
this is a very unlikely case to happen so moving to RHEL-6.7.
How long did you wait before restarting libvirt? Could you attach the libvirt logs here?
(In reply to Giuseppe Scrivano from comment #2)
> this is a very unlikely case to happen so moving to RHEL-6.7.
>
> How long did you wait before restarting libvirt? Could you attach the
> libvirt logs here?
Several hours, longer than the time of a clone job.
Comment 9Giuseppe Scrivano
2014-12-14 14:46:26 UTC
as the problem cannot be reproduced on newer versions and that it depends on a very unlikely sequence of commands, I am going to close it.