Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1467920 - Rebase to SQLAlchemy 1.1.11
Rebase to SQLAlchemy 1.1.11
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-sqlalchemy (Show other bugs)
12.0 (Pike)
Unspecified Unspecified
medium Severity medium
: Upstream M2
: 12.0 (Pike)
Assigned To: Michael Bayer
Marian Krcmarik
: Rebase, Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-05 09:59 EDT by Michael Bayer
Modified: 2018-02-05 14:10 EST (History)
7 users (show)

See Also:
Fixed In Version: python-sqlalchemy-1.1.11-1.el7ost
Doc Type: Rebase: Enhancements Only
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-13 16:37:25 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:3462 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-15 20:43:25 EST

  None (edit)
Description Michael Bayer 2017-07-05 09:59:59 EDT
There are some performance enhancements in the 1.1 series that stabilized as of 1.1.7, which specifically impact openstack services particularly Neutron which makes heavy use of the "joined eager loading" feature to a much larger extent in successive versions (mitaka, newton, etc), discussion at [1] [2] and followup fixes at [3].

There's no risk in going to 1.1.11 vs. 1.1.7, nor is there risk going just to 1.1.7 for now, the bug fixes between 1.1.7 and 1.1.11 are inert from an openstack perspective.



[1] https://bitbucket.org/zzzeek/sqlalchemy/issues/3915
[2] http://lists.openstack.org/pipermail/openstack-dev/2017-February/112381.html
[3] https://bitbucket.org/zzzeek/sqlalchemy/issues/3947
Comment 5 errata-xmlrpc 2017-12-13 16:37:25 EST
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-2017:3462

Note You need to log in before you can comment on or make changes to this bug.