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

Bug 1200986

Summary: sqlalchemy object reuse breaks multi-backend
Product: Red Hat OpenStack Reporter: Eric Harney <eharney>
Component: openstack-cinderAssignee: Eric Harney <eharney>
Status: CLOSED ERRATA QA Contact: Yogev Rabl <yrabl>
Severity: high Docs Contact:
Priority: medium    
Version: 7.0 (Kilo)CC: eharney, mlopes, scohen, sgotliv, yeylon
Target Milestone: ga   
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-cinder-2015.1.0-2.el7ost Doc Type: Bug Fix
Doc Text:
Prior to this update, SQLAlchemy objects were incorrectly shared between multiple 'cinder-volume' processes. Consequently, SQLAlchemy connections would fail when using a Block Storage multi-backend, resulting in database-related errors in the volume service. This fix re-initializes SQLAlchemy connections when forking 'cinder-volume' child processes. As a result multi-backend now works as expected.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 13:22:12 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:

Description Eric Harney 2015-03-11 18:39:43 UTC
When configuring Cinder for multi-backend, unsafe sqlalchemy usage causes database errors.

Need to ensure that this gets patched in Cinder or oslo.db.

This likely will not be seen before Kilo (7.0) even though the code in prior versions is not correct.

Comment 6 Yogev Rabl 2015-06-28 14:42:59 UTC
verified in version
openstack-cinder-2015.1.0-3.el7ost.noarch
python-cinder-2015.1.0-3.el7ost.noarch

Comment 8 errata-xmlrpc 2015-08-05 13:22:12 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.

https://access.redhat.com/errata/RHEA-2015:1548