Verification of 2024.1/stable Sunbeam on Noble of Watcher version
2:12.0.0-0ubuntu1.3 has been completed. The test setup has been running
the patched code for 21+ hours and the original issue is no longer
present:
=== Check 1: No QueuePool TimeoutError in decision-engine logs ===
ubuntu@watcher-test:~$ sudo k8s kubectl logs -n openstack watcher-0 -c
watcher-decision-engine \
--since=60m | grep -iEc "queuepool|TimeoutError"
0
=== Check 2: Sleeping MySQL connections are not accumulating ===
ubuntu@watcher-test:~$ sudo k8s kubectl exec -n openstack
watcher-mysql-router-0 -c mysql-router -- \
env MYSQL_PWD=GQRMYf0Ty30er2ZEaoic0wM6 \
mysql -u relation-181_a5fd8d428d564-180 \
-h watcher-mysql-router-service.openstack.svc.cluster.local \
-P 6446 watcher_api \
-e "SELECT count(*), state FROM information_schema.processlist GROUP BY
state;"
count(*) state
4
1 executing
=== Check 3: watcher-decision-engine reports ACTIVE ===
ubuntu@watcher-test:~$ openstack optimize service list
+----+-------------------------+-----------+--------+
| ID | Name | Host | Status |
+----+-------------------------+-----------+--------+
| 1 | watcher-decision-engine | watcher-0 | ACTIVE |
| 2 | watcher-applier | watcher-0 | ACTIVE |
+----+-------------------------+-----------+--------+
These results demonstrate that the initial issue of accumulating MySQL
connections resulting in a watcher pod failure has been solved.
verification-done-noble
verification-done-caracal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086710
Title:
watcher's use of apscheduler is incompatible with python 3.12 and
eventlet
To manage notifications about this bug go to:
https://bugs.launchpad.net/watcher/+bug/2086710/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
