yahoo-eng-team team mailing list archive

[Akhil Gudise <1884068@xxxxxxxxxxxxxxxxxx>]

Actually the compute service state is down and the compute filter is
also disabled. So I've enabled the Compute Filter and tested it again,
as Sean has mentioned that VM will be moved to the Error state because
compute filter sorts the unavailable hosts and it happened and This
turns out that the bug is invalid. Sorry for posting an invalid Bug.

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

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

Title:
  Instance stuck in build state when some/one compute node is
  unreachable

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Description
  ===========
  Instance stuck in build state when some/one compute node is unreachable in an Availability Zone and this situation arises when the scheduler picks up the compute node which is unreachable and the instance is stuck in the build state not even moving to the error state.

  NOTE: unreachable means that either the compute node is shutoff or
  might be some network connectivity issue.

  Steps to reproduce
  ==================
  * Create instance X by providing an Availability Zone. 
  * where this Availability zone should consist of a group of compute nodes in which I have a single 
    reachable(Power ON) compute node and 3 unreachable(Power OFF) compute nodes.  
  * OR even you can try powering off all the compute nodes in that zone.

      $ openstack server create --image <img> --flavor <flavor>
  --network <n/w> --availability-zone <AZ> <ServerName>

  Expected result
  ===============
  The instance X should fail to build with proper error message if all the compute nodes are unreachable or it should deploy the instance on the reachable compute nodes.

  Actual result
  =============
  The instance is in the "BUILD" state forever.

  Environment
  ===========
  1. Stein release used.

     $ rpm -qa | grep nova-compute
       openstack-nova-compute-19.1.0-1

  2. KVM hypervisor version: 1.5.3

  2. LVM used as storage backend on the Compute host.
     lvm2-2.02.185

  3. Which networking type did you use?
     Neutron with OpenVSwitch

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