Bug 1666832 - CPU live migration quick-fail has no effect
Summary: CPU live migration quick-fail has no effect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z5
: 13.0 (Queens)
Assignee: Artom Lifshitz
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-16 16:59 UTC by Artom Lifshitz
Modified: 2023-03-21 19:10 UTC (History)
7 users (show)

Fixed In Version: openstack-nova-17.0.9-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-14 13:54:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0565 0 None None None 2019-03-14 13:54:33 UTC

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


Note You need to log in before you can comment on or make changes to this bug.