Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1060771 - nova does not read sql db config option
nova does not read sql db config option
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova (Show other bugs)
4.0
Unspecified Unspecified
urgent Severity urgent
: z2
: 4.0
Assigned To: Xavier Queralt
Ami Jeain
: Triaged, ZStream
Depends On: 1060687 1060783
Blocks:
  Show dependency tree / graph
 
Reported: 2014-02-03 09:50 EST by Fabio Massimo Di Nitto
Modified: 2016-04-26 15:09 EDT (History)
10 users (show)

See Also:
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 14:05:31 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-2014:0231 normal SHIPPED_LIVE Moderate: openstack-nova security and bug fix update 2014-03-04 19:00:29 EST

  None (edit)
Description Fabio Massimo Di Nitto 2014-02-03 09:50:56 EST 
+++ 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 09:54:37 EST 
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 08:04:32 EST 
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 14:05:31 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.

http://rhn.redhat.com/errata/RHSA-2014-0231.html
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.