Comment 6 for bug 1562863

The patches from upstream [1], [2] provide only partial fix of the original issue. Before applying patches the command "nova-manage db archive_deleted_rows" doesn't move the entries to the shadow tables at all because of foreign key constraint issue. After applying patch [1] nova-manage firstly process tables that don't have foreign keys. Patch [2] fixes issue with archiving instance_actions and instance_actions_event. And after applying those two patches we are able to archive some tables, but archiving tables with foreign key constraint issue, like 'instances', still fails.

Here is the output from MOS 9.1: http://paste.openstack.org/show/577672/

So, as we can see, 'instances' table still contain rows with 'deleted' non-zero values, but, for example 'instance_actions' and 'instance_actions_event' tables are empty after running "nova-manage db archive_deleted_rows".

[1] https://review.openstack.org/#/c/246635/
[2] https://review.openstack.org/#/c/326730/