diff options
| author | Vishvananda Ishaya <vishvananda@gmail.com> | 2012-09-23 17:13:44 +0000 |
|---|---|---|
| committer | Vishvananda Ishaya <vishvananda@gmail.com> | 2012-09-23 17:22:57 +0000 |
| commit | 4a97a743c41e53d7278590e75913ff761ea319db (patch) | |
| tree | c29188c87546e929b31aa403e92b909cea1159ec /nova/openstack | |
| parent | 338fae4f2be127f65491860fc46dc7436a5610be (diff) | |
| download | nova-4a97a743c41e53d7278590e75913ff761ea319db.tar.gz nova-4a97a743c41e53d7278590e75913ff761ea319db.tar.xz nova-4a97a743c41e53d7278590e75913ff761ea319db.zip | |
Allow deletion of instance with failed vol cleanup
If something goes wrong when trying to delete volumes that have
been marked delete_on_terminate, we leave an instance record in
the database that can't be removed even though the instance is
gone.
Intelligent recovery at this point is very difficult, so for now
just log a warning and let the instance be deleted. It is unfortunate
that there isn't a good way to let the user know that his volume
was not deleted, but this seems preferable to leaving an undeletable
instance.
A test is included to verify the behavior, as well as a note so that
a better fix can be included later.
Fixes bug 1055095
Change-Id: I26e801fc3e9c56cf84d2b977295fcf580428879a
Diffstat (limited to 'nova/openstack')
0 files changed, 0 insertions, 0 deletions