Bug 1060687
| Summary: | DB connection error code 2013 not handled | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Fabio Massimo Di Nitto <fdinitto> | |
| Component: | openstack-cinder | Assignee: | Flavio Percoco <fpercoco> | |
| Status: | CLOSED ERRATA | QA Contact: | Dafna Ron <dron> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 4.0 | CC: | dnavale, eharney, fdinitto, fpercoco, gfidente, yeylon | |
| Target Milestone: | z4 | Keywords: | ZStream | |
| Target Release: | 4.0 | Flags: | pm-rhel:
internal-review+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-cinder-2013.2.3-1.el6ost | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, due to an un-handled connection error status code, the reconnect operation for Block Storage service was not triggered. This resulted in an issue from the High-Availability stand point as the nodes would fail to reconnect once the database was back up.
As a fix, this status code is added to the list of connection error status codes in the database library.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1060771 1060783 (view as bug list) | Environment: | ||
| Last Closed: | 2014-05-29 19:57:27 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: | ||||
| Bug Blocks: | 1060771, 1060783 | |||
|
Description
Fabio Massimo Di Nitto
2014-02-03 11:14:28 UTC
It appears that RHOS 4 may support this under the [database] section with names max_retries/retry_interval or sql_max_retries/sql_retry_interval, but I haven't tried this yet. http://git.openstack.org/cgit/openstack/cinder/tree/cinder/openstack/common/db/sqlalchemy/session.py?h=stable/havana#n301 http://git.openstack.org/cgit/openstack/cinder/tree/cinder/openstack/common/db/sqlalchemy/session.py?h=stable/havana#n332 Seems to be a similar issue as bug 1060685, Havana Cinder's sample conf generation isn't accurate. Flavio did the debug and those options appears not to be read at all. I doubled check in your box and it seems like they are indeed filed under the database section. Somehow, I missed that when I was debugging it this morning.
./openstack/common/db/sqlalchemy/session.py: cfg.IntOpt('max_retries',
./openstack/common/db/sqlalchemy/session.py: deprecated_name='sql_max_retries',
./openstack/common/db/sqlalchemy/session.py: remaining = CONF.database.max_retries
Could you please retry by setting those values under the database section?
[database] max_retries = -1 retry_interval = 1 mysql down: ==> scheduler.log <== 2014-02-03 16:51:50.956 16184 CRITICAL cinder [-] (OperationalError) (2013, "Lost connection to MySQL server at 'reading initial communication packet', system error: 0") None None so still doesn´t work :) Erm, I think the issue is that 2013 is not part of the listed codes here[0] [0] http://git.openstack.org/cgit/openstack/cinder/tree/cinder/openstack/common/db/sqlalchemy/session.py?h=stable/havana#n548 verified using openstack-cinder-2013.2.3-1.el6ost.noarch 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 |