Bug 671337 - Unable to restart domain on crash with on_crash="rename-restart"
Summary: Unable to restart domain on crash with on_crash="rename-restart"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xen
Version: 5.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Miroslav Rezanina
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 666800 666802
TreeView+ depends on / blocked
 
Reported: 2011-01-21 09:42 UTC by Miroslav Rezanina
Modified: 2011-07-21 12:07 UTC (History)
4 users (show)

Fixed In Version: xen-3.0.3-123.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-21 09:13:34 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1070 0 normal SHIPPED_LIVE xen bug fix and enhancement update 2011-07-21 09:12:56 UTC

Description Miroslav Rezanina 2011-01-21 09:42:12 UTC
Description of problem:
When we set on_crash parameter to rename-restart, domain is not able to restart when crash. xend.log shows following error:



Version-Release number of selected component (if applicable):
xen-3.0.3-122.el5

How reproducible:
always

Steps to Reproduce:
1. set domain config option on_crash="rename-restart"
2. boot domain
3. crash domain using echo c > /proc/sysrq-trigger
  
Actual results:
Domain is renamed but not restarted.

Expected results:
Domain is renamed and restarted.

Additional info:
This is regression caused by patch  "Remove overhead when checking duplicate devices". As we now check against data xend cache, we hit data of crashed domain. As we perform rename-restart, we rename domain, change its uuid and clear xenstore. However, we hold XendDomainInfo.info structure intact so it can be reused.

Comment 1 Miroslav Rezanina 2011-01-21 09:54:23 UTC
Xend.log error (missed in initial comment):


[2011-01-21 10:53:17 xend.XendDomainInfo 7152] ERROR (XendDomainInfo:2829) Failed to restart domain 9.
Traceback (most recent call last):
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 2812, in restart
    new_dom = XendDomain.instance().domain_create(config)
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 245, in domain_create
    dominfo = XendDomainInfo.create(config)
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 236, in create
    vm.initDomain()
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 2154, in initDomain
    self.createDevices()
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 2410, in createDevices
    self.createDevice(n, c)
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1503, in createDevice
    self.device_duplicate_check(deviceClass, devconfig)
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 697, in device_duplicate_check
    raise VmError('The uname "%s" is already used by another domain' %
VmError: The uname "/var/lib/xen/images/lws/rhel55-64pv.img" is already used by another domain

Comment 9 errata-xmlrpc 2011-07-21 09:13:34 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-1070.html

Comment 10 errata-xmlrpc 2011-07-21 12:07:03 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-1070.html


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