During the get_networks method of ML2, we iterate over each network and do a database call to lookup the segments for that network. This scales the number of database calls linearly with the number of retrieved networks.
*** Bug 1292166 has been marked as a duplicate of this bug. ***
Verified (Tempest_run)[stack@instack neutron]$ rpm -qa |grep neutron openstack-neutron-common-7.0.1-6.el7ost.noarch openstack-neutron-7.0.1-6.el7ost.noarch python-neutron-7.0.1-6.el7ost.noarch openstack-neutron-ml2-7.0.1-6.el7ost.noarch openstack-neutron-openvswitch-7.0.1-6.el7ost.noarch python-neutronclient-3.1.0-1.el7ost.noarch https://rhos-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhos-unittest-gerrit-neutron-rhel-7.2/719/testReport/
@Haim, since this bug did not affect OSP 7 or earlier versions, it did not affect any existing customers. Since we're fixing it before the first release of OSP 8, it means that no one was affected by the regression, so we don't need doctext (Because there's no one to tell that the issue was fixed).
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/RHEA-2016-0603.html