Public bug reported:
Description
===========
For example:
Theres compute Nodes: A and B and C
instance "vmtest" runs on A now.
Steps to reproduce
==================
1.nova host-evacuate A
2.Assumed instance "vmtest" evacuated failed on B with libvirt error. And found
the instance xml of vmtest is still in /etc/libvirt/qemu
3.Then try again "nova host-evacuate A".If vmtest is scheduled on B again,
there will throw exception: Instance instance-vmtest already exists.
Expected result
===============
When vmtest first evacuated failed on B, remove instance xml of vmtest on B
Actual result
=============
If vmtest is scheduled on B again, there will throw exception: Instance
instance-vmtest already exists.
Whether it should be clean up the instance xml of vmtest on the failed
evacuated node B?
Environment
===========
openstack mitaka
** Affects: nova
Importance: Undecided
Status: New
** Tags: evacuate mitaka
--
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/1784798
Title:
openstack mitaka evacuate fails and no clean up the evacuated instance
xml in libvirt
Status in OpenStack Compute (nova):
New
Bug description:
Description
===========
For example:
Theres compute Nodes: A and B and C
instance "vmtest" runs on A now.
Steps to reproduce
==================
1.nova host-evacuate A
2.Assumed instance "vmtest" evacuated failed on B with libvirt error. And
found the instance xml of vmtest is still in /etc/libvirt/qemu
3.Then try again "nova host-evacuate A".If vmtest is scheduled on B again,
there will throw exception: Instance instance-vmtest already exists.
Expected result
===============
When vmtest first evacuated failed on B, remove instance xml of vmtest on B
Actual result
=============
If vmtest is scheduled on B again, there will throw exception: Instance
instance-vmtest already exists.
Whether it should be clean up the instance xml of vmtest on the failed
evacuated node B?
Environment
===========
openstack mitaka
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1784798/+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
