Hide Forgot
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
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