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.
Created attachment 1979993[details]
The daemon log for the steps above
Description of problem:
As subject
Version-Release number of selected component (if applicable):
libvirt-9.5.0-3.el9.x86_64
qemu-kvm-8.0.0-9.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Prepare two hosts for migration. Start a guest on one host
2. Migrate the VM with --copy-storage-all
➜ ~ virsh migrate --live rhel-9.2 qemu+ssh://root$DEST/system --copy-storage-all
3. At the same time of step2, try to cancel the migration by blockjob --abort
➜ ~ virsh blockjob rhel-9.2 vda --abort
error: Requested operation is not valid: domain is not running
Actual results:
As above
Expected results:
Although "blockjob --abort" should not cancel the migration, it should return the operation unsupported err directly.
Additional info:
Note that this behaviour is exactly the same as any other command which would modify the state of the VM, such as unplugging a device.
The blockjob itself is considered internal for the use of the migration.
In the above description I don't see any form of justification why we should treat the blockjobs differently than anything else, could you please elaborate?
Created attachment 1979993 [details] The daemon log for the steps above Description of problem: As subject Version-Release number of selected component (if applicable): libvirt-9.5.0-3.el9.x86_64 qemu-kvm-8.0.0-9.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1. Prepare two hosts for migration. Start a guest on one host 2. Migrate the VM with --copy-storage-all ➜ ~ virsh migrate --live rhel-9.2 qemu+ssh://root$DEST/system --copy-storage-all 3. At the same time of step2, try to cancel the migration by blockjob --abort ➜ ~ virsh blockjob rhel-9.2 vda --abort error: Requested operation is not valid: domain is not running Actual results: As above Expected results: Although "blockjob --abort" should not cancel the migration, it should return the operation unsupported err directly. Additional info: