yahoo-eng-team team mailing list archive

[Tina Kevin <song.ruixia@xxxxxxxxxx>]

Public bug reported:

Description
===========
Live migration is not update instance numa hugepages info in xml.
if the numa hugepages info of source host is different from the
numa hugepages info of destation host, then instance in destation
host can not start normally, result in the live-migration is failed.

Steps to reproduce
==================
A chronological list of steps which will bring off the
issue:
* There are two compute nodes(host1 and host2).
  The two hosts have same numa topolopy and all have two numa nodes,
  each numa node has eight cpus.

* I boot two instances(A and B) to the compute nodes, instance A
  is located on host1 and instance B is located on host2.
  The two instances are all dedicated cpu_policy and use hugepages.
  Each instance has eight cpus. Instance A is located on the numa node1
  of host1 and instance B is located on the numa node1 of host2.

* Then I live migrate the instance A, the scheduler selects the numa
node2  of host2, but because of the numa hugepages info of xml is not
updated, the instance in destation host starts error.

Expected result
===============
The live-migration of the instance is success.

Actual result
=============
The live-migration of the instance is failed.
The reason is that the numa hugepages info of xml is not updated.

Environment
===========
1. Exact version of OpenStack
 Mitaka

2. Which hypervisor did you use?
 Libvirt + KVM

3. Which networking type did you use?
 Neutron with OpenVSwitch

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: hugepages live-migration numa

** Tags added: hugepages live-migration numa

** Description changed:

  Description
  ===========
  Live migration is not update instance numa hugepages info in xml.
- if the numa hugepages info of source host is different from the 
+ if the numa hugepages info of source host is different from the
  numa hugepages info of destation host, then instance in destation
  host can not start normally, result in the live-migration is failed.
- 
  
  Steps to reproduce
  ==================
  A chronological list of steps which will bring off the
  issue:
- * I boot an instance with dedicated cpu_policy and hugepages
- * then I live migrate the instance
- * then the live-migration action is failed
+ * There are two compute nodes(host1 and host2).
+   The two hosts have same numa topolopy and all have two numa nodes,
+   each numa node has eight cpus.
  
- * There are two compute nodes(host1 and host2). 
-   The two hosts have same numa topolopy and all have two numa nodes, 
-   each numa node has eight cpus.
+ * I boot two instances(A and B) to the compute nodes, instance A
+   is located on host1 and instance B is located on host2.
+   The two instances are all dedicated cpu_policy and use hugepages.
+   Each instance has eight cpus. Instance A is located on the numa node1
+   of host1 and instance B is located on the numa node1 of host2.
  
- * I boot two instances(A and B) to the compute nodes, instance A 
-   is located on host1 and instance B is located on host2.
-   The two instances are all dedicated cpu_policy and use hugepages. 
-   Each instance has eight cpus. Instance A is located on the numa node1 
-   of host1 and instance B is located on the numa node1 of host2.
- 
- * Then I live migrate the instance A, the scheduler selects the numa node2 of host2, 
-   but because of the numa hugepages info of xml is not updated, the instance in destation
-   host starts error.
+ * Then I live migrate the instance A, the scheduler selects the numa node2 of host2,
+   but because of the numa hugepages info of xml is not updated, the instance in destation
+   host starts error.
  
  Expected result
  ===============
  The live-migration of the instance is success.
  
  Actual result
  =============
  The live-migration of the instance is failed.
  The reason is that the numa hugepages info of xml is not updated.
  
  Environment
  ===========
- 1. Exact version of OpenStack 
-  Mitaka
+ 1. Exact version of OpenStack
+  Mitaka
  
  2. Which hypervisor did you use?
-  Libvirt + KVM
+  Libvirt + KVM
  
  3. Which networking type did you use?
-  Neutron with OpenVSwitch
+  Neutron with OpenVSwitch

** Description changed:

  Description
  ===========
  Live migration is not update instance numa hugepages info in xml.
  if the numa hugepages info of source host is different from the
  numa hugepages info of destation host, then instance in destation
  host can not start normally, result in the live-migration is failed.
  
  Steps to reproduce
  ==================
  A chronological list of steps which will bring off the
  issue:
  * There are two compute nodes(host1 and host2).
    The two hosts have same numa topolopy and all have two numa nodes,
    each numa node has eight cpus.
  
  * I boot two instances(A and B) to the compute nodes, instance A
    is located on host1 and instance B is located on host2.
    The two instances are all dedicated cpu_policy and use hugepages.
    Each instance has eight cpus. Instance A is located on the numa node1
    of host1 and instance B is located on the numa node1 of host2.
  
- * Then I live migrate the instance A, the scheduler selects the numa node2 of host2,
-   but because of the numa hugepages info of xml is not updated, the instance in destation
-   host starts error.
+ * Then I live migrate the instance A, the scheduler selects the numa
+ node2  of host2, but because of the numa hugepages info of xml is not
+ updated, the instance in destation host starts error.
  
  Expected result
  ===============
  The live-migration of the instance is success.
  
  Actual result
  =============
  The live-migration of the instance is failed.
  The reason is that the numa hugepages info of xml is not updated.
  
  Environment
  ===========
  1. Exact version of OpenStack
   Mitaka
  
  2. Which hypervisor did you use?
   Libvirt + KVM
  
  3. Which networking type did you use?
   Neutron with OpenVSwitch

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1607996

Title:
  Live migraion is not update numa hugepages info in xml

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  Live migration is not update instance numa hugepages info in xml.
  if the numa hugepages info of source host is different from the
  numa hugepages info of destation host, then instance in destation
  host can not start normally, result in the live-migration is failed.

  Steps to reproduce
  ==================
  A chronological list of steps which will bring off the
  issue:
  * There are two compute nodes(host1 and host2).
    The two hosts have same numa topolopy and all have two numa nodes,
    each numa node has eight cpus.

  * I boot two instances(A and B) to the compute nodes, instance A
    is located on host1 and instance B is located on host2.
    The two instances are all dedicated cpu_policy and use hugepages.
    Each instance has eight cpus. Instance A is located on the numa node1
    of host1 and instance B is located on the numa node1 of host2.

  * Then I live migrate the instance A, the scheduler selects the numa
  node2  of host2, but because of the numa hugepages info of xml is not
  updated, the instance in destation host starts error.

  Expected result
  ===============
  The live-migration of the instance is success.

  Actual result
  =============
  The live-migration of the instance is failed.
  The reason is that the numa hugepages info of xml is not updated.

  Environment
  ===========
  1. Exact version of OpenStack
   Mitaka

  2. Which hypervisor did you use?
   Libvirt + KVM

  3. Which networking type did you use?
   Neutron with OpenVSwitch

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1607996/+subscriptions