evacuate an instance on non-shared storage succeeded and boot image is rebuilt
Bug #2020028 reported by
norman shen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Description
===========
evacuate an instance on non-shared storage succeeded and boot image is rebuilt
Steps to reproduce
==================
1. Create a two compute nodes cluster without shared storage
2. boot a image backed virtual machine
3. shutdown down the compute node where vm is running
4. evacuate instance to another node
Expected:
evacuate failed
Real:
evacuate succeeded and boot image is rebuilt.
Version
===============
Using nova victoria version
Revision history for this message
| sean mooney (sean-k-mooney) wrote | #1 |
| Changed in nova: | |
| status: | New → Invalid |
To post a comment you must log in.
This is the expected behavior.
evacuate of image-backed vms rebuilds the root disk because that is the expected behaviour in a cloud env where the instance root disk should not contain any valuable data.
This is functioning precisely how the API was designed to work.
in fact, the preservation fo disk for BFV or instance with shared storage is perhaps the more surprising aspect.
evacuate should be assumed to be destructive unless you are using boot form volume.
it may or may not be destructive depending on the storage configuration of the compute ndoes when used with non boot from volume instnaces.