cpu pining fails with 1 sibling cpu set and 2 single cpu set

Bug #1657791 reported by Ritesh Paiboina
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
In Progress
Low
Ritesh Paiboina

Bug Description

Description
===========

CPU pinning fails when the sibling set consists of single VCPUS and a sibling set.
For example,

CoercedSet([45]), CoercedSet([31]), CoercedSet([1, 25])

Considering a case,
When a compute with NUMA NODE 1 which has 4 VCPU and 16GB RAM available to use.

And when you to try to launch a instance with a flavor of 4 VCPU and 16GB RAM, it is failed to launch i.e "message": "No valid host was found. There are not enough hosts available."

Total Available VCPUS
1,3,5,7,9,11,13,15,17,19,21,25,27,29,31,33,35,37,39,41,43,45
Used VCPUS
3,5,7,9,11,13,15,17,19,21,27,29,33,35,37,39,41,43
Free VCPUS
1,25,31,45

VCPUS STATISTICS
Total : 22
Usage : 18
Free : 4

siblings=set([21,45]),set([7,31]),set([15,39]),set([11,35]),set([17,41]),set([3,27]),set([13,37]),set([9,33]),set([19,43]),set([5,29]),set([1,25])])

1, 25 , 31 and 45 VCPUS are available to use but nova could not able to use them.

As 31 and 45 are not siblings , Nova is not considering them to boot the VM.
Because of Numa Topology Filter returns with 0 hosts available.

Steps to reproduce
==================

We have 22 VCPUS available for Pinning in NUMA NODE 1.

1. Launch an instance with 1 VCPU
2. Launch an instance with 1 VCPU
3. Launch an instance with 8 VCPU
4. Launch an instance with 8 VCPU
5. Launch an instance with 4 VCPU

Expected result
===============

Instance should be in active state

Actual result
=============

Instance is in Error state.
| fault | {"message": "No valid host was found. There are not enough hosts available.", "code": 500, "details": " File \"/usr/lib/python2.7/dist-packages/nova/conductor/manager.py\", line 397, in build_instances |

Environment
===========
1. Exact version of OpenStack you are running.

   Mitaka Stable

2. Which hypervisor did you use?
   Libvirt + KVM

2. Which storage type did you use?
   None

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

Changed in nova:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/423334

description: updated
Revision history for this message
Stephen Finucane (stephenfinucane) wrote :

This has already been fixed on master and is included in the newton release. Unfortunately, I don't think we can backport this to Mitaka (which only accepts high priority fixes now). I'll try, but you may need to carry this patch yourself (or ask your vendor to do so).

Revision history for this message
Stephen Finucane (stephenfinucane) wrote :

FYI - here are the fixes:

master (Ocata): https://review.openstack.org/#/c/342709/7
stable/newton: https://review.openstack.org/#/c/373889/

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by Ritesh (<email address hidden>) on branch: master
Review: https://review.openstack.org/423334
Reason: Already fixed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.