The instances which didn't be evacuated will be destroyed when the nova-compute service is restarted.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Undecided
|
Margarita Shakhova |
Bug Description
Description
===========
Normally, if you finished evacuating instance, nova-compute will destroy the existed instances whose state are "done" or "accept" in the migration table from the fault host after the nova-compute service is restarted. However, if the nova-scheduler failed to schedule the hosts, e.g. no valid host, nova-scheduler won't update the migration state of the instance to "failed", so that the nova-compute will destroy this instance after restarting by mistake.
Steps to reproduce
==================
1. Create some instances in the the specific host.
2. Make this host to fault state.
3. Disable nova-compute service in other hosts, aim to mock that nova-scheduler fail to schedule.
4. Recover the fault host and restart nova-compute.
5. Check all instances are still existed in the kvm.
Expected result
===============
All instances should be still existed in the kvm.
Actual result
=============
All instances are destroyed by nova-compute unfortunately.
Changed in nova: | |
assignee: | nobody → alex (chinabjalex) |
Changed in nova: | |
status: | In Progress → New |
Changed in nova: | |
status: | New → In Progress |
Changed in nova: | |
status: | New → Confirmed |
Changed in nova: | |
assignee: | nobody → Margarita Shakhova (shakhova-margarita) |
Can you please attach logs to this bug?