← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1396456] Re: instance boot failed when restart host

 

Do you have more detail? How can we reproduce this bug?

** Also affects: nova/icehouse
   Importance: Undecided
       Status: New

** Changed in: nova
       Status: New => Incomplete

** Changed in: nova/icehouse
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1396456

Title:
  instance boot failed when restart host

Status in OpenStack Compute (Nova):
  Incomplete
Status in OpenStack Compute (nova) icehouse series:
  Incomplete

Bug description:
  When I reboot host, state of one instance became ERROR with CLI(nova
  list).


  The log of the nova-compute service:
  2014-11-25 12:13:48.095 3848 DEBUG nova.compute.manager [-] [instance: 7d7ec3f2-3709-4bbc-b278-849fd672d284] Current state is 4, state in DB is 1. _init_instance /usr/lib/python2.7/site-packages/nova/compute/manager.py:961

  But:
  2014-11-25 12:14:48.249 3848 ERROR nova.virt.libvirt.driver [-] An error occurred while trying to launch a defined domain with xml: <domain type='kvm'>
    <name>instance-00000006</name>
    <uuid>7d7ec3f2-3709-4bbc-b278-849fd672d284</uuid>
    .........

  Check the log of libvirt:
  2014-11-25 04:14:18.997+0000: 2545: error : qemuMonitorOpenUnix:313 : monitor socket did not show up: No such file or directory

  Use stable-icehouse.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1396456/+subscriptions


References