I think this bug was considered fixed because at the time once the patch
addressing was merged, the bug automatically went into fix committed.
It should therefore be re-opened. Even if tweaking sql pool parameters
avoids the issue, this should be considered more of a mitigation rather
than a
I recently ran into this bug while trying to concurrently boot a large number
(75) of VMs:
https://bugs.launchpad.net/neutron/+bug/1160442
I see that the fix for the bug added configuration of SQLAlchemy QueuePool
parameters that should prevent the boot failures I was seeing. However, I