Bug 1319385

Summary: [RFE] nova scheduler should re-calculate the cpus on the destination compute while Migrating a dedicated/cpu-pinned instance
Product: Red Hat OpenStack Reporter: Anand Nande <anande>
Component: openstack-novaAssignee: Eoghan Glynn <eglynn>
Status: CLOSED DUPLICATE QA Contact: nlevinki <nlevinki>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0 (Kilo)CC: berrange, dasmith, eglynn, jraju, jschluet, kchamart, sbauza, sferdjao, sgordon, srevivo, vromanso
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: sgordon: needinfo? (eglynn)
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-18 19:47:28 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:

Description Anand Nande 2016-03-19 10:08:49 UTC 
Description of problem:

[This is just a clone of an upstream BZ]
https://bugs.launchpad.net/nova/+bug/1417667

Currently in OSP7, this is not present, hence migrating
(live/cold) fails if there are other instances using
the same cpu-range on the destination compute node.

As a result, the instance can only be started after
making sure the existing/running instance stop using
the vcpu(and hence the pcpus its assigned to).
Comment 5 Stephen Gordon 2017-01-18 19:47:28 UTC 

*** This bug has been marked as a duplicate of bug 1222414 ***