Bug 1666832

Summary:	CPU live migration quick-fail has no effect
Product:	Red Hat OpenStack	Reporter:	Artom Lifshitz <alifshit>
Component:	openstack-nova	Assignee:	Artom Lifshitz <alifshit>
Status:	CLOSED ERRATA	QA Contact:	OSP DFG:Compute <osp-dfg-compute>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	dasmith, eglynn, jhakimra, kchamart, sbauza, sgordon, vromanso
Target Milestone:	z5	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-nova-17.0.9-2.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-14 13:54:24 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:

Description Artom Lifshitz 2019-01-16 16:59:39 UTC

Description of problem:

Quick fail of CPU pinning live migration not actually preventing multiple instances being pinned to same host CPU.

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


How reproducible:


Steps to Reproduce:

1. Have a deployment with 2 computes

2. Set vcpu_pin_set to 1 to ensure instances are pinned to a specific CPU

3. Boot 2 instances with hw:cpu_policy dedicated.

4. Observe them being pinned to CPU 1, one instance per compute host

5. Set vcpu_pin_set to 0, 1 to allow live migration by creating a free CPU on the computes.

6. Live migrate one of the instances

Actual results:

Live migration succeeded, both instances are pinned to CPU 1.

Expected results:

Live migration should fail because CPU 1 is already in used on the destination host.

Additional info:

Comment 11 errata-xmlrpc 2019-03-14 13:54:24 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://access.redhat.com/errata/RHBA-2019:0565