Bug 681113 - Destroying a migrated guest on target host causes 'Error shutting down domain'
Summary: Destroying a migrated guest on target host causes 'Error shutting down domain'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-01 06:35 UTC by zhanghaiyan
Modified: 2011-05-19 13:48 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-19 13:48:00 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0637 0 normal SHIPPED_LIVE virt-manager bug fix and enhancement update 2011-05-18 17:55:47 UTC

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


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