Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1060771

Summary:	nova does not read sql db config option
Product:	Red Hat OpenStack	Reporter:	Fabio Massimo Di Nitto <fdinitto>
Component:	openstack-nova	Assignee:	Xavier Queralt <xqueralt>
Status:	CLOSED ERRATA	QA Contact:	Ami Jeain <ajeain>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.0	CC:	breeler, dallan, eharney, ndipanov, sgordon, sradvan, vpopovic, xqueralt, yeylon
Target Milestone:	z2	Keywords:	Triaged, ZStream
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-nova-2013.2.1-6.el6ost	Doc Type:	Bug Fix
Doc Text:	Previously, the database backend did not handle the MySQL error code 2013 (Lost connection). As a result, when an error code was not recognized in the database backend, the connection was not restored even if we specified a retry interval in the configuration. Thus, although the error was related to losing the connection, Compute was not trying to reconnect. This was fixed by adding the MySQL error code 2013 to the known database error codes. Now the MySQL error code is properly handled by the backend.	Story Points:	---
Clone Of:	1060687	Environment:
Last Closed:	2014-03-04 19:05:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1060687, 1060783
Bug Blocks:

Description Fabio Massimo Di Nitto 2014-02-03 14:50:56 UTC

+++ This bug was initially created as a clone of Bug #1060687 +++

As part of the RHOS High Availability we need to tune connections to database and qpid.

Some of those options include daemons startup behavior and specifically:

max_retries = -1
retry_interval = 1

to allow the daemon to continue retrying connecting.

This is a blocker to deploy cinder in HA environments and must be fixed asap.

Comment 1 Fabio Massimo Di Nitto 2014-02-03 14:54:37 UTC

Extra info:

starting nova-consoleauth with db offline will result in a python traceback. Other part of openstack will at least attempt to connect 10 times.

Comment 3 Ami Jeain 2014-02-19 13:04:32 UTC

verified although there is a new issue. Nova is not able to move the spawning instance to Active. User will have to boot a new instance.
Opening a new bug on this one

Comment 5 errata-xmlrpc 2014-03-04 19:05:31 UTC

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.

http://rhn.redhat.com/errata/RHSA-2014-0231.html