nova evacaute action will destroy the vm if the vm is migrate back but the migration it not completed
Bug #2027669 reported by
efineshi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Incomplete
|
Undecided
|
efineshi |
Bug Description
for example:
1. the compte node's network is disconnected。the compute lost connection to the controller and it was down.
2. evacuted the servers from the the failed compute node. and manual distroy all the servers in the node.
3. the compute node's network is reconected。
4. we migrate the servers back to compute node.
5. restert the nova-compute, the servers will be destroy cause of the migration action is not completed before and it think the servers are dirty.
Changed in nova: | |
assignee: | nobody → efineshi (efineshi) |
description: | updated |
To post a comment you must log in.
Thanks for submitting this bug, but it is incomplete and can not be treated without the following information. Please add them to the ticket.
- steps to reproduce
- the version of Nova and the novaclient (or os-client)
- logs (on debug level)
- environment details depending on the bug
libvirt/kvm versions, VMWare version, ...
storage type (ceph, LVM, GPFS, ...)
network type (nova-network or neutron)
For bug reporting assistance, use OpenStack's Bug template available at: https:/ /wiki.openstack .org/wiki/ Nova/BugsTeam/ BugReportTempla te.