Ask Your Question

Howto clean out failed instance migrations for nova

asked 2016-01-12 05:35:03 -0600

theque42 gravatar image

updated 2016-01-12 09:35:55 -0600

I've been running instance live-migration on my centos/liberty cloud (controller, neutron, 2xcompute) and it seems to fail every time, when it worked in my previous fedora install.

Also, the failed migrations arent cleaned out properly, so my logs are now filling up with:

nova.compute.resource_tracker....Migration instance not found: Instance 61b9fd41-79a9-4fba-a423-8314999fb678 could not be found

How do I clean these out? Reading logs, it seems that there is logic for performing cleanout of failed instances of some sort, but it doesnt seem to be capable of cleaning out mine...

There are no instances defined when viewing through horizon dashboard, and none are shown via nova list Any help appreciated! TQ

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2016-01-13 05:59:43 -0600

Vinoth gravatar image

You can login to the DB and modify the instance details as deleted.

Login Mysql > nova DB > instances table > UUID of uncleaned VM row.

In that row, compare the row of properly deleted VM with the row you are going to modify. Then make the appropriate changes and save it.

P.S: - I use Mysql workbench tool to access the mariaDB of OpenStack.



edit flag offensive delete link more


Thanks! I was afraid I would have to manually hack the DB. I was hoping that the nova-manage program (or similar would be able to validate all instances in DB, and clean out any non existing. That would be a quite logical feature me thinks.. :-) (Or at least simply nova-manage --delete UUID)

theque42 gravatar imagetheque42 ( 2016-01-14 03:55:23 -0600 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2016-01-12 05:35:03 -0600

Seen: 1,305 times

Last updated: Jan 13 '16