Description of problem:
We have problem that nova-scheduler fails to connect to RabbitMQ after environment restart, because it needs to process some significant amount of data from "nova" MySQL database.
With 1 million records in the "nova.instances", it takes ~40 minutes for nova-scheduler to finish the startup.
Version-Release number of selected component (if applicable):
openstack-nova-api-2015.1.4-12.el7ost.noarch
openstack-nova-cert-2015.1.4-12.el7ost.noarch
openstack-nova-common-2015.1.4-12.el7ost.noarch
openstack-nova-compute-2015.1.4-12.el7ost.noarch
openstack-nova-conductor-2015.1.4-12.el7ost.noarch
openstack-nova-console-2015.1.4-12.el7ost.noarch
openstack-nova-novncproxy-2015.1.4-12.el7ost.noarch
openstack-nova-scheduler-2015.1.4-12.el7ost.noarch
How reproducible:
There are already some Bugzilla Bugs created regarding this issue:
Add DB cleanup functionality to nova-manage. - https://bugzilla.redhat.com/show_bug.cgi?id=1154875
nova-manage db archive_deleted_rows doesn't work - https://bugzilla.redhat.com/show_bug.cgi?id=1285359
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2017-0282.html