*** This bug is a duplicate of bug 1666831 ***
https://bugs.launchpad.net/bugs/1666831
** This bug has been marked a duplicate of bug 1666831
Nova recreates instance directory after migration/resize
--
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/1592015
Title:
libvirt: cleanup of a volume backed instance resize leaves behind the
instance directory
Status in OpenStack Compute (nova):
In Progress
Bug description:
Description
===========
Attempts to cleanup a volume backed instance resize leaves behind the
instance directory and additional disk files. This seems to relate to the
following change and the additional imagebackend calls made in _cleanup_resize :
libvirt: Fix/implement revert-resize for RBD-backed images
https://review.openstack.org/#/c/228505/
Steps to reproduce
==================
* Create a volume backed instance.
* Shutdown the instance.
* resize/migrate the instance to another host.
* Review the instance directory on the source host.
Expected result
===============
The instance directory on the source host is removed.
Actual result
=============
The instance directory on the source host remains and is also populated with
a previously unused `disk` file and disk.info file.
Environment
===========
1. Exact version of OpenStack you are running. See the following
# git rev-parse HEAD
6e2e1dc912199e057e5c3a5e07d39f26cbbbdd5b
2. Which hypervisor did you use?
libvirt + kvm
2. Which storage type did you use?
(For example: Ceph, LVM, GPFS, ...)
LVM/iSCSI
3. Which networking type did you use?
N/A
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1592015/+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
