yahoo-eng-team team mailing list archive

[Majid <mhormati@xxxxxxxxx>]

Public bug reported:

We have deployed OpenStack Icehouse with Legacy Networking setup and we are building our instances on shared storage (NFS). We want to protect VMs when a host (compute node) fails. When we use Nova Evacuate API with "--on-shared-storage" option two issues happens:
1- Sometimes the evacuated VM will come up on new host but it will be re-built from the base image. 
2- Sometimes the instance will not come up at all. For this case if we use "nova reboot --hard <VM>" the VM will come up on the new host.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Issues with Nova Evacuate API

Status in OpenStack Compute (Nova):
  New

Bug description:
  We have deployed OpenStack Icehouse with Legacy Networking setup and we are building our instances on shared storage (NFS). We want to protect VMs when a host (compute node) fails. When we use Nova Evacuate API with "--on-shared-storage" option two issues happens:
  1- Sometimes the evacuated VM will come up on new host but it will be re-built from the base image. 
  2- Sometimes the instance will not come up at all. For this case if we use "nova reboot --hard <VM>" the VM will come up on the new host.

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