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.

Bug 681113

Summary: Destroying a migrated guest on target host causes 'Error shutting down domain'
Product: Red Hat Enterprise Linux 6 Reporter: zhanghaiyan <yoyzhang>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: dallan, dyuan, hjiang, llim, mliu, mzhan, xen-maint
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 13:48:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description zhanghaiyan 2011-03-01 06:35:08 UTC 
Description of problem:
Destroying a migrated guest on target host can succeed but causes 'Error shutting down domain'

Version-Release number of selected component (if applicable):
- kernel-2.6.32-117.el6.x86_64
- qemu-kvm-0.12.1.2-2.147.el6.x86_64
- libvirt-0.8.7-8.el6.x86_64
- virt-manager-0.8.6-2.el6.noarch

How reproducible:
8/8

Steps to Reproduce:
1. Migrate a guest from source host (A) to target host (B)
2. On host A, remote connect to host B via virt-manager, then could see the migrated guest is running on host B 
3. In virt-manager, right click the guest, select 'Shut down'-> 'Force off', could see 'Are you sure you want to force poweroff $guest ?', click 'yes'  
  
Actual results:
3. The guest is destroyed, but the following error pops up
Error shutting down domain: Domain not found: no domain with matching uuid '6d272c96-2025-bfea-87f9-a91867efc49b'
Details
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 908, in _do_destroy_domain
    vm.destroy()
  File "/usr/share/virt-manager/virtManager/domain.py", line 1088, in destroy
    self._update_status()
  File "/usr/share/virt-manager/virtManager/domain.py", line 1274, in _update_status
    info = self.get_info()
  File "/usr/share/virt-manager/virtManager/domain.py", line 967, in get_info
    return self._backend.info()
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 823, in info
    if ret is None: raise libvirtError ('virDomainGetInfo() failed', dom=self)
libvirtError: Domain not found: no domain with matching uuid '6d272c96-2025-bfea-87f9-a91867efc49b'

Expected results:
No error pops up

Additional info:
Execute virsh command # virsh destroy $guest on host B can destroy the guest successfully without error
Comment 2 Cole Robinson 2011-03-09 18:45:58 UTC 
This can be more easily tested by creating a transient guest with virsh and shutting it down in virt-manager:

virsh dumpxml $someguest > foo.xml
virsh undefine $someguest
virsh create foo.xml
(shutdown the guest in virt-manager, see the error).
Comment 3 Cole Robinson 2011-03-10 16:40:55 UTC 
Fixed in virt-manager-0.8.6-3.el6
Comment 5 Huming Jiang 2011-03-17 03:27:03 UTC 
Verfied it on build :
virt-manager-0.8.6-3.el6.noarch
libvirt-0.8.7-13.el6.x86_64
qemu-kvm-0.12.1.2-2.150.el6.x86_64
kernel-2.6.32-120.el6.x86_64

Steps:
1. Prepare an VM which is not running;

2. Input "virsh dumpxml $someguest > foo.xml" in the terminal;

3. Input "virsh undefine $someguest" in the terminal;

4. Input "virsh create foo.xml" in the terminal;

5. Force off your guest.

Verification is passed.
Comment 6 mliu 2011-04-18 05:40:45 UTC 
Verfied it Pass on build :
virt-manager-0.8.6-3.el6.noarch
libvirt-0.8.7-17.el6.x86_64
qemu-kvm-0.12.1.2-2.153.el6.x86_64
kernel-2.6.32-130.el6.x86_64
Comment 7 errata-xmlrpc 2011-05-19 13:48:00 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0637.html