Bug 1360846
| Summary: | Default DB connections is too low | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Gorka Eguileor <geguileo> | |
| Component: | python-oslo-db | Assignee: | Damien Ciabrini <dciabrin> | |
| Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | high | |||
| Version: | 8.0 (Liberty) | CC: | apevec, dciabrin, lhh, mbayer | |
| Target Milestone: | async | Keywords: | ZStream | |
| Target Release: | 8.0 (Liberty) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | python-oslo-db-2.6.0-4.el7ost | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1360858 (view as bug list) | Environment: | ||
| Last Closed: | 2016-09-14 14:41:57 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: | 1360858 | |||
|
Description
Gorka Eguileor
2016-07-27 15:59:59 UTC
Validation instructions: The fix only consists in an updated default config for oslo.db. Since all OpenStack services rely on that for accessing the DB, I think a simple validation would consist in: 1. making sure max overflow setting is updated from 15 to 50 in oslo.db defult config: grep -B1 'sql_max_overflow' usr/lib/python2.7/site-packages/oslo_db/options.py 2. making sure regular services are up and running on the undercloud (e.g. by running nova list...), 3. creating a test stack on the overcloud or a ping test with tripleo.sh [root@controller-0 yum.repos.d]# grep -B1 'sql_max_overflow' /usr/lib/python2.7/site-packages/oslo_db/options.py
default=50,
deprecated_opts=[cfg.DeprecatedOpt('sql_max_overflow',
All openstack services are running on the undercloud
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/RHBA-2016-1867.html |