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.
** Changed in: nova
Status: New => Invalid
--
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/2020028
Title:
evacuate an instance on non-shared storage succeeded and boot image is
rebuilt
Status in OpenStack Compute (nova):
Invalid
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2020028/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
