Bug 1378906 – nova-scheduler fails to start because of the too big nova database

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1378906 - nova-scheduler fails to start because of the too big nova database

Summary:	nova-scheduler fails to start because of the too big nova database

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-nova (Show other bugs)
Sub Component:
Version:	7.0 (Kilo)
Hardware:	Unspecified Unspecified

Priority	high Severity medium
Target Milestone:	async
Target Release:	7.0 (Kilo)
Assigned To:	Dan Smith
QA Contact:	Gabriel Szasz
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-09-23 09:31 EDT by Robin Cernin
Modified:	2017-11-20 13:07 EST (History)
CC List:	15 users (show)

See Also:
Fixed In Version:	openstack-nova-2015.1.4-16.el7ost
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-02-15 17:56:43 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2017:0282	normal	SHIPPED_LIVE	Moderate: openstack-cinder, openstack-glance, and openstack-nova security update	2017-02-15 22:52:44 EST

Groups: None (edit)

Description Robin Cernin 2016-09-23 09:31:15 EDT

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:

Comment 4 Dave Maley 2016-10-20 16:53:25 EDT

customer has confirmed the fix provided here has resolved the issue in their environment

Comment 8 errata-xmlrpc 2017-02-15 17:56:43 EST

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

Note You need to log in before you can comment on or make changes to this bug.