Issues with Nova Evacuate API
Bug #1362244 reported by
Majid
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
jichenjc |
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-
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.
tags: | added: compute |
Changed in nova: | |
assignee: | nobody → jichenjc (jichenjc) |
Changed in nova: | |
milestone: | none → kilo-1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | kilo-1 → 2015.1.0 |
To post a comment you must log in.
Hi, thanks for your bug report. We need additional information to help diagnose the issue.
On 1, what is the behavior you expect when the VM comes up on the new host, other than being rebuilt from the base image?
On 2, can you check in the nova-compute.log on the origin host and the new host to look for ERROR messages related to the migrated VM? There should be messages there that indicate what went wrong so we can pinpoint the problem.