Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1224950

Summary: [NUMA][CPU Pinning] simultaneous boot of multiple instances leads to cpu pinning overlap
Product: Red Hat OpenStack Reporter: Nikola Dipanov <ndipanov>
Component: openstack-novaAssignee: Sahid Ferdjaoui <sferdjao>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: high Docs Contact:
Priority: high    
Version: 6.0 (Juno)CC: berrange, dasmith, eglynn, kchamart, ndipanov, sbauza, sferdjao, sgordon, vromanso, yeylon
Target Milestone: z5Keywords: ZStream
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-nova-2014.2.3-56.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1226365 (view as bug list) Environment:
Last Closed: 2016-03-23 14:26:14 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: 1226365    

Description Nikola Dipanov 2015-05-26 09:47:48 UTC
Description of problem:

Due to improper usage of a critical section - there is a race condition that can cause 2 instance to end up pinned to the same CPU. See upsream LP bug for more details/

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

Upstream Kilo is affected, but since RHOS 6 has the CPU pinning feature backported, it is affected too in all versions

How reproducible:

Race condition so it will depend on a number of factors, it is more likely to happen under load (starting several VMs requesting CPU pinning in parallel, that end up on the same compute host)

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

There is no overlap in pinned CPUs for any of the instances

Additional info:

Comment 11 errata-xmlrpc 2016-03-23 14:26:14 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0500.html