Verified test plan for Caracal on Jammy Observed results:
Version 1:22.0.1-0ubuntu1.3~cloud0: - No hard connection pool exhaustion or "ERROR: Internal Error" seen on client requests, even when increasing request count to 200 over 5 tries - However, log inspection confirms the connection leak is actively occurring: 2026-10-14 05:29:07.757 66954 ERROR sqlalchemy.pool.impl.QueuePool [-] Exception during reset or similar: AssertionError: do not call blocking functions from the mainloop - This is due to the fact that Jammy uses Python 3.10, which has a different garbage collection threshold than Python 3.12, so the unexecuted query object is less frequently swept directly inside Eventlet's mainloop context. While this prevents rapid pool exhaustion under light testing, the AssertionErrors in the logs prove connection slots are still being leaked. -------------------------------------------------------------------------- Version 1:22.0.1-0ubuntu1.4~cloud0 (-proposed): - No Internal Errors from any request - "openstack stack list" succeeds - No new "Exception during reset" or TimeoutError entries in the log ** Tags removed: verification-caracal-needed ** Tags added: verification-caracal-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2168828 Title: heat-engine DB connection pool exhaustion after stack delete or snapshot list To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2168828/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
