Description of problem:
Due to multiple migrations of instances as a part of maintenance activity, nova migration-list contains data from the point the system was initially built, this means that there are transactions listed from 2016 till the present day.
Is there any way we can control the size of Nova migrations table?
Version-Release number of selected component (if applicable):
How reproducible:
Migrate instances and check if the record found in nova migration-list can be deleted/removed considering how old they are?
Steps to Reproduce:
# nova migration-list --host <hostname>
Actual results:
Currently, nova migration-list shows entire data right when first migration was performed.
Expected results:
nova migration-list should show the list of migrated instances as per specified date/time
OR
Is there any way to remove old migration list record from the database.
Additional info:
Is it possible to delete/remove an old list from the database, Any idea where this list gets stored?
Hi all,
Nova already has a cron job that is supposed to purge data such as that which is described within this Bugzilla.
The cron job does not succeed if /var/log/nova/nova-manage.log is owned by root rather than Nova. Please set ownership of that log file to nova.
Kind regards,
Paul.