Bug 1060783 - heat does not read sql db config option
Summary: heat does not read sql db config option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-heat
Version: 4.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: z4
: 4.0
Assignee: Steven Hardy
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On: 1060687
Blocks: 1060771
TreeView+ depends on / blocked
 
Reported: 2014-02-03 15:36 UTC by Fabio Massimo Di Nitto
Modified: 2016-04-26 14:05 UTC (History)
11 users (show)

Fixed In Version: openstack-heat-2013.2.2-2.el6ost
Doc Type: Bug Fix
Doc Text:
Previously, the database 'Lost connection' errors were not handled properly. As a result, certain configuration options related to database connection retries did not work, specifically, setting the 'max_retries' parameter did not result in reconnection attempts as expected. With this update, the database session handles the 'Lost connection' errors and the 'max_retries' option now works as expected. So when a 'Lost connection' error occurs, database reconnection is attempted.
Clone Of: 1060687
Environment:
Last Closed: 2014-05-29 19:57:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1275838 0 None None None Never
OpenStack gerrit 73314 0 None None None Never
Red Hat Product Errata RHBA-2014:0577 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform 4 Bug Fix and Enhancement Advisory 2014-05-29 23:55:40 UTC

Description Fabio Massimo Di Nitto 2014-02-03 15:36:48 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.

[database]
# maximum db connection retries during startup. (setting -1
# implies an infinite retry count) (integer value)
max_retries=-1

# interval between retries of opening a sql connection
# (integer value)
retry_interval=1

[root@rhos4-heat1 heat]# /etc/init.d/openstack-heat-engine start
with mysql down, will result in a traceback (this is with or without max_retries/retry_interval
Comment 1 Steven Dake 2014-02-03 15:42:15 UTC 
Steve,

Could you look at a retry feature?

Thanks
-steve
Comment 8 Steven Dake 2014-04-20 13:21:12 UTC 
Isn't this bug fixed by the latest rebase?
Comment 9 Amit Ugol 2014-04-24 04:47:23 UTC 
Verified that error 2013 was added.
Comment 10 Steven Hardy 2014-04-24 11:06:51 UTC 
(In reply to Steven Dake from comment #8)
> Isn't this bug fixed by the latest rebase?

I should be, yes, I believe Amit has now verified that the patch is present in the openstack-heat-2013.2.2-2.el6ost package, ref comment #9 and discussions on IRC.
Comment 13 errata-xmlrpc 2014-05-29 19:57:37 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/RHBA-2014-0577.html
Note You need to log in before you can comment on or make changes to this bug.