Scheduling a vm to a reporting compute node cause the number of vms in the compute node exceed the limit
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Medium
|
tianxiang ai |
Bug Description
Description
===========
When scheduling a vm to a reporting compute node,
update_
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_
Steps to reproduce
==================
1,create a new az,there is noly one compute node in this az;
2,set max_instances_
3,boot 100 vms to this az, the vms will be scheduled to the specified node;
4,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.
Changed in nova: | |
status: | New → In Progress |
assignee: | nobody → tianxiang ai (aitianxiang) |
description: | updated |
summary: |
- Schedule a vm to a reporting compute node + Scheduler a vm to a reporting compute node |
summary: |
- Scheduler a vm to a reporting compute node + Scheduling a vm to a reporting compute node cause the number of vms in + the compute node exceed the limit |
Fix proposed to branch: master /review. opendev. org/700529
Review: https:/