How to identify data inconsistency errors in openstack databases?

asked 2015-03-17 14:07:29 -0500

adisarun gravatar image

updated 2015-03-17 16:33:46 -0500

OpenStack Operations Guide talks about some of the potential data inconsistency errors in openstack databases.

"... an instance was terminated, but the status was not updated in the database" [1]

"Sometimes an instance is terminated but the floating IP was not correctly de-associated from that instance. Because the database is in an inconsistent state, the usual tools to dissaociate the IP no longer work. To fix this, you must manually update the database." [2]

I'm wondering whether manually inspecting the database is the only way to identify such data inconsistency errors. If so, I think it could be a tedious process since we have a large number of tables in each openstack component database and may not clearly know which ones should be queried to detect the potential inconsistencies.

[1] http://docs.openstack.org/openstack-ops/content/maintenance.html (http://docs.openstack.org/openstack-o...)

[2] http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html (http://docs.openstack.org/openstack-o...)

edit retag flag offensive close merge delete