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.
Bug 633697 - virsh domjobabort displays error information for aborting domain save job
Summary: virsh domjobabort displays error information for aborting domain save job
Keywords:
Status: CLOSED DUPLICATE of bug 639595
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Osier Yang
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-14 09:27 UTC by Alex Jia
Modified: 2010-11-16 06:29 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-16 06:29:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alex Jia 2010-09-14 09:27:52 UTC
Description of problem:
virsh domjobabort displays error information for aborting domain save job, in fact, domjobinfo and domjobabort operations support migrate and save job, however, libvirt source codes exist hard code for migration in libvirt-0.8.4 tar package:

 ......

 5039 static int
 5040 qemuDomainWaitForMigrationComplete(struct qemud_driver *driver, virDomainObjPtr vm)
 5041 {
 ......

 5150         case QEMU_MONITOR_MIGRATION_STATUS_CANCELLED:
 5151             priv->jobInfo.type = VIR_DOMAIN_JOB_CANCELLED;
 5152             qemuReportError(VIR_ERR_OPERATION_FAILED,
 5153                             "%s", _("Migration was cancelled by client"));
 5154             break;
 5155         }
 ......


Whether we may add a QEMU_MONITOR_SAVE_STATUS_CANCELLED, and then:

          case QEMU_MONITOR_SAVE_STATUS_CANCELLED:
              priv->jobInfo.type = VIR_DOMAIN_JOB_CANCELLED;
              qemuReportError(VIR_ERR_OPERATION_FAILED,
                              "%s", _("Saving was cancelled by client"));
              break;
          }

or giving variable to for Migration and Saving. 
  
Version-Release number of selected component (if applicable):
# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.0 (Santiago)

# rpm -q libvirt
libvirt-0.8.1-27.el6.x86_64


How reproducible:
always

Steps to Reproduce:
1. open the first terminal and run virsh save example example.sav
2. open the second terminal and run virsh domjobabort example
  
Actual results:
# virsh domjobabort example

# virsh save example example.sav
error: Failed to save domain example to example.sav
error: operation failed: Migration was cancelled by client


Expected results:
correctly display

Additional info:
libvirt-0.8.4.tar.gz

Comment 2 Osier Yang 2010-11-16 06:29:02 UTC

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


Note You need to log in before you can comment on or make changes to this bug.