yahoo-eng-team team mailing list archive

[tianxiang ai <1857448@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
===========
When scheduling a vm to a reporting compute node,
update_available_resource will clear self.stats and update compute_nodes
table in db firstly, and update this table after calculating all
instances on this node. At this moment, the scheduler filter will pass
this node because there is no num_instances in compute_nodes.stats.


Steps to reproduce
==================
1,create a new az,there is noly one compute node in this az;
2,set max_instances_per_host = 100 on the compute node;
3,boot 100 vms to this az, the vms will be scheduled to the specified node;
4,set max_instances_per_host = 80 on this compute node;
5,boot some vms to this az once again.

Expected result
===============
boot vm fails and return no valid host error


Actual result
=============
some vms failed but some vms will be scheduled to the compute node successfully when the compute node is reporting available resources.

** Affects: nova
     Importance: Undecided
     Assignee: tianxiang ai (aitianxiang)
         Status: In Progress

** Changed in: nova
       Status: New => In Progress

** Changed in: nova
     Assignee: (unassigned) => tianxiang ai (aitianxiang)

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

Title:
  Schedule a vm to a reporting compute node

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  Description
  ===========
  When scheduling a vm to a reporting compute node,
  update_available_resource will clear self.stats and update compute_nodes
  table in db firstly, and update this table after calculating all
  instances on this node. At this moment, the scheduler filter will pass
  this node because there is no num_instances in compute_nodes.stats.


  Steps to reproduce
  ==================
  1,create a new az,there is noly one compute node in this az;
  2,set max_instances_per_host = 100 on the compute node;
  3,boot 100 vms to this az, the vms will be scheduled to the specified node;
  4,set max_instances_per_host = 80 on this compute node;
  5,boot some vms to this az once again.

  Expected result
  ===============
  boot vm fails and return no valid host error

  
  Actual result
  =============
  some vms failed but some vms will be scheduled to the compute node successfully when the compute node is reporting available resources.

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