Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-3161

"sqlalchemy.exc.TimeoutError: QueuePool limit of size 5 overflow 50 reached, connection timed out, timeout 30.00" error raised after repeated calls of Flavor.get_* methods

XMLWordPrintable

    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • Committed
    • openstack-nova-27.1.1-18.0.20231120204705.b5e4390.el9ost
    • Committed
    • Committed
    • None
    • Release Note Not Required
    • Moderate

      +++ This bug was initially created as a clone of Bug #2222998 +++

      Description of problem:

      This is a copy of upstream bug:

      https://bugs.launchpad.net/nova/+bug/2027755

      where repeated calls involving "get" of 'flavors' table records eventually raise the error:

      sqlalchemy.exc.TimeoutError: QueuePool limit of size 5 overflow 50 reached, connection timed out, timeout 30.00 (Background on this error at: https://sqlalche.me/e/14/3o7r)

      Version-Release number of selected component (if applicable):

      16.x

      How reproducible:

      Always

      Steps to Reproduce:

      1. Run 'watch -n 1 openstack flavor list --all --long' and eventually the errors will appear in the nova-api log

      Actual results:

      Eventual error of "sqlalchemy.exc.TimeoutError: QueuePool limit of size 5 overflow 50 reached, connection timed out, timeout 30.00 (Background on this error at: https://sqlalche.me/e/14/3o7r)" in nova-api log and 500 status code returned to user

      Expected results:

      No errors

      — Additional comment from RHEL Program Management on 2023-07-14 20:05:20 UTC —

      This item has been properly Triaged and planned for the release, and Target Release is now set to match the release flag. For details, see https://mojo.redhat.com/docs/DOC-1195410

      — Additional comment from Artom Lifshitz on 2023-07-17 16:19:08 UTC —

      Moving to 17.1.2 as it's not yet merged on master, and 17.1.1 will be exceptions only, and we can't have regressions between 16.2.6 and 17.1.1.

      — Additional comment from RHEL Program Management on 2023-07-17 16:19:20 UTC —

      This item has been properly Triaged and planned for the release, and Target Release is now set to match the release flag.

      — Additional comment from Ian Frangs on 2023-08-03 15:46:23 UTC —

      If you think customers need a description of this bug in addition to the content of the BZ summary field, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text.

      If this bug does not require an additional Doc Text description, please set the 'requires_doc_text' flag to '-'.

      If the BZ already has Doc Text, please perform a quick review. Update it if needed.

      — Additional comment from melanie witt on 2023-08-17 04:53:01 UTC —

      This BZ is not yet VERIFIED and will not have Doc Text until then.

              mwitt@redhat.com melanie witt
              jira-bugzilla-migration RH Bugzilla Integration
              rhos-dfg-compute
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: