Bug 1332907

Summary: CPU isolated thread policy is not working properly.
Product: [Community] RDO Reporter: Ricardo Noriega <rnoriega>
Component: openstack-novaAssignee: Prasanth Anbalagan <panbalag>
Status: CLOSED EOL QA Contact: nlevinki <nlevinki>
Severity: high Docs Contact:
Priority: unspecified    
Version: trunkCC: berrange, dasmith, eglynn, jjung, rbryant, rnoriega, sbauza, sferdjao, sgordon, srevivo, vromanso
Target Milestone: ---   
Target Release: Kilo   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1333195 1333196 (view as bug list) Environment:
Last Closed: 2016-05-19 15:40:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1333195, 1333196    

Description Ricardo Noriega 2016-05-04 10:49:50 UTC 
Description of problem:

Isolated thread policy is not working properly according to documentation.

Version-Release number of selected component (if applicable):


How reproducible:

Highly

Steps to Reproduce:

 Check https://bugs.launchpad.net/nova-solver-scheduler/+bug/1578150

Actual results:

 Sibling threads are used when the correspondent thread is ocuppied by an isolated vCPU.

Expected results:

 Have one thread per core unused.

Additional info:

 Check https://bugs.launchpad.net/nova-solver-scheduler/+bug/1578150
Comment 1 Chandan Kumar 2016-05-19 15:40:38 UTC 
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.