yahoo-eng-team team mailing list archive

[Jason Hobbs <jason.hobbs@xxxxxxxxxxxxx>]

Public bug reported:

Description
===========
A instance did not come up properly the first time it was started and had to be manually killed and then restarted through the API to get it to work.


Steps To Reproduce
==================
* I started an instance through the API
* I noticed I coudln't connect to its floating IP.
* I checked the nova compute node and the qemu-kvm process was running at 100% cpu, and its console log was empty.
* I tried to shut it down through virsh on the compute node, but it didn't respond to that.
* I had to kill it with kill <pid>.
* After that I started the instance again through the API and it came up properly and everything is working.

Expected Result
===============
The instance starts correctly the first time.

Actual Result
=============
I had to kill and restart the instance.

This doesn't happen everytime, seems to be some kind of race.

I'm at a bit of a loss as to how to debug this.


Environment
===========
This is with mitaka running on xenial using libvirt+kvm hypervisor, openvswitch networking, and no attached volumes.

Package versions:
ii  nova-common                          2:13.1.2-0ubuntu2                   all          OpenStack Compute - common files
ii  nova-compute                         2:13.1.2-0ubuntu2                   all          OpenStack Compute - compute node base
ii  nova-compute-kvm                     2:13.1.2-0ubuntu2                   all          OpenStack Compute - compute node (KVM)
ii  nova-compute-libvirt                 2:13.1.2-0ubuntu2                   all          OpenStack Compute - compute node libvirt support
ii  python-nova                          2:13.1.2-0ubuntu2                   all          OpenStack Compute Python libraries
ii  python-novaclient                    2:3.3.1-2ubuntu1                    all          client library for OpenStack Compute API - Python 2.7
ii  libvirt-bin                          1.3.1-1ubuntu10.6                   amd64        programs for the libvirt library
ii  libvirt0:amd64                       1.3.1-1ubuntu10.6                   amd64        library for interfacing with different virtualization systems
ii  python-libvirt                       1.3.1-1ubuntu1                      amd64        libvirt Python bindings

Linux hayward-44 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: oil-guestos-fail

** Attachment added: "sosreport-hayward-44-20170126201325.tar.xz"
   https://bugs.launchpad.net/bugs/1659648/+attachment/4809483/+files/sosreport-hayward-44-20170126201325.tar.xz

-- 
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/1659648

Title:
  Instance hung on first start, but works after being killed and
  restarted

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  A instance did not come up properly the first time it was started and had to be manually killed and then restarted through the API to get it to work.

  
  Steps To Reproduce
  ==================
  * I started an instance through the API
  * I noticed I coudln't connect to its floating IP.
  * I checked the nova compute node and the qemu-kvm process was running at 100% cpu, and its console log was empty.
  * I tried to shut it down through virsh on the compute node, but it didn't respond to that.
  * I had to kill it with kill <pid>.
  * After that I started the instance again through the API and it came up properly and everything is working.

  Expected Result
  ===============
  The instance starts correctly the first time.

  Actual Result
  =============
  I had to kill and restart the instance.

  This doesn't happen everytime, seems to be some kind of race.

  I'm at a bit of a loss as to how to debug this.

  
  Environment
  ===========
  This is with mitaka running on xenial using libvirt+kvm hypervisor, openvswitch networking, and no attached volumes.

  Package versions:
  ii  nova-common                          2:13.1.2-0ubuntu2                   all          OpenStack Compute - common files
  ii  nova-compute                         2:13.1.2-0ubuntu2                   all          OpenStack Compute - compute node base
  ii  nova-compute-kvm                     2:13.1.2-0ubuntu2                   all          OpenStack Compute - compute node (KVM)
  ii  nova-compute-libvirt                 2:13.1.2-0ubuntu2                   all          OpenStack Compute - compute node libvirt support
  ii  python-nova                          2:13.1.2-0ubuntu2                   all          OpenStack Compute Python libraries
  ii  python-novaclient                    2:3.3.1-2ubuntu1                    all          client library for OpenStack Compute API - Python 2.7
  ii  libvirt-bin                          1.3.1-1ubuntu10.6                   amd64        programs for the libvirt library
  ii  libvirt0:amd64                       1.3.1-1ubuntu10.6                   amd64        library for interfacing with different virtualization systems
  ii  python-libvirt                       1.3.1-1ubuntu1                      amd64        libvirt Python bindings

  Linux hayward-44 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

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