Bug 1200986 - sqlalchemy object reuse breaks multi-backend
Summary: sqlalchemy object reuse breaks multi-backend
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ga
: 7.0 (Kilo)
Assignee: Eric Harney
QA Contact: Yogev Rabl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-11 18:39 UTC by Eric Harney
Modified: 2016-04-26 15:59 UTC (History)
5 users (show)

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.
Clone Of:
Environment:
Last Closed: 2015-08-05 13:22:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1417018 0 None None None Never
OpenStack gerrit 163551 0 None None None Never
Red Hat Product Errata RHEA-2015:1548 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2015-08-05 17:07:06 UTC

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
Note You need to log in before you can comment on or make changes to this bug.