| opendevreview | Marios Andreou proposed openstack/watcher-specs master: Add 2025.1 spec for prometheus as datasource in watcher https://review.opendev.org/c/openstack/watcher-specs/+/933300 | 10:18 |
|---|---|---|
| sean-k-mooney | i am seeing some sqlalchemy isssues with eventlet on master https://paste.opendev.org/show/bGPgfURx1cZYOsgmtDyw/ | 19:34 |
| sean-k-mooney | im wonderign if this is a py3.12 issue | 19:36 |
| opendevreview | Ghanshyam proposed openstack/watcher master: Update gate jobs as per the 2025.1 cycle testing runtime https://review.opendev.org/c/openstack/watcher/+/932963 | 19:45 |
| sean-k-mooney | gmann: thanks im hopping to see if the local db issue im seeeing is related to noble or not based on that new ci run | 19:47 |
| gmann | ack | 19:47 |
| gmann | sean-k-mooney: are you seeing that on multinode ? because single node watcher-tempest-functional job running fine on noble | 19:49 |
| sean-k-mooney | yep 3 node devstack all-in-one + 2 computes | 19:50 |
| gmann | i see | 19:50 |
| sean-k-mooney | after a while i start gettign 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/20/3o7r | 19:51 |
| sean-k-mooney | more specifically im seing this https://paste.opendev.org/show/b5C2Zz4A4BFIGbKLKrQU/ | 19:51 |
| sean-k-mooney | the first tracebacke made me think that perhaps it is not monky patching properly | 19:55 |
| sean-k-mooney | but the code is not referencing watcher in teh traceback | 19:55 |
| sean-k-mooney | the second error i think is because we are leakign the conenctions when they fail with the first runtime error | 19:56 |
| sean-k-mooney | so sometime i see File "/opt/stack/data/venv/lib/python3.12/site-packages/oslo_log/pipe_mutex.py", line 82, in acquire | 20:54 |
| sean-k-mooney | in the error but nor normally | 20:55 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!