Performed verification of 2024.1/stable Sunbeam on Noble with Watcher
version 2:12.0.0-0ubuntu1.3. I was able to reproduce the issue on
watcher 2:12.0.0-0ubuntu1.1. After upgrading to watcher
2:12.0.0-0ubuntu1.3, the issue was no longer present over a 24-hour
period.
=== Check 1: No QueuePool TimeoutError in decision-engine logs ===
ubuntu@sunbeam-dev:~$ 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@sunbeam-dev:~$ sudo k8s kubectl exec -n openstack watcher-mysql-router-0
-c mysql-router -- env MYSQL_PWD='cnmEzayK7Z3bdJMdW4AtaizP' mysql -u
relation-197_31edbe7658a24-195 -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
Number of connections remained low during test period
=== Check 3: watcher-decision-engine reports ACTIVE ===
ubuntu@sunbeam-dev:~$ openstack optimize service list
+----+-------------------------+-----------+--------+
| ID | Name | Host | Status |
+----+-------------------------+-----------+--------+
| 1 | watcher-applier | watcher-0 | ACTIVE |
| 2 | watcher-decision-engine | watcher-0 | ACTIVE |
+----+-------------------------+-----------+--------+
These results are consistent with the original issue being resolved in
Watcher 2:12.0.0-0ubuntu1.3.
--
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:
[SRU] 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/cloud-archive/caracal/+bug/2086710/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
