yahoo-eng-team team mailing list archive

[Facundo Maldonado <facundo.n.maldonado@xxxxxxxxx>]

Public bug reported:

Environment: 
- fresh devstack multinode installation using nova-network.
- one controller node with a compute node (node_1) 
- one compute node (node_2)

Both compute nodes has different cpu info features.

When live migrating from node_1 to node_2 an InvalidCPUInfo is raised in live_mirgate method in conductor's manager.
The exception is not captured and the roll back of the task_state is not performed. 
The instance stays in 'migrating' state.

** Affects: nova
     Importance: Undecided
     Assignee: Facundo Maldonado (facundo-n-maldonado)
         Status: New


** Tags: live-migration

** Changed in: nova
     Assignee: (unassigned) => Facundo Maldonado (facundo-n-maldonado)

-- 
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/1294210

Title:
  InvalidCPUInfo exception not catched in conductor _live_migrate

Status in OpenStack Compute (Nova):
  New

Bug description:
  Environment: 
  - fresh devstack multinode installation using nova-network.
  - one controller node with a compute node (node_1) 
  - one compute node (node_2)

  Both compute nodes has different cpu info features.

  When live migrating from node_1 to node_2 an InvalidCPUInfo is raised in live_mirgate method in conductor's manager.
  The exception is not captured and the roll back of the task_state is not performed. 
  The instance stays in 'migrating' state.

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