Comment 7 for bug 1930151

so, nope, not related:
that move is for W, and we're on the UC, no pacemaker there anyway.

haproxy shows mysql backend as up 2 minutes before the crash[0] - and, fun thing, it seems the mistral_db_sync is able to access the DB for a while and then, crash:

Jun 16 08:29:52 undercloud haproxy[7]: Backup Server mysql/undercloud.ctlplane.localdomain is UP, reason: Layer4 check passed, check duration: 0ms. 0 active and 1 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.

When the mistral_db_sync crashes, we can see the following time: 08:32:01

There is no mysql activity around that time in haproxy log[1].

[0] https://8f87caa881e8eda0ef3b-848f29e6bb7f92a80e59238721ad95f7.ssl.cf5.rackcdn.com/periodic/opendev.org/openstack/tripleo-heat-templates/stable/ussuri/tripleo-ci-centos-8-undercloud-upgrade-ussuri/75847b1/logs/undercloud/var/log/containers/stdouts/mistral_db_sync.log
[1] https://8f87caa881e8eda0ef3b-848f29e6bb7f92a80e59238721ad95f7.ssl.cf5.rackcdn.com/periodic/opendev.org/openstack/tripleo-heat-templates/stable/ussuri/tripleo-ci-centos-8-undercloud-upgrade-ussuri/75847b1/logs/undercloud/var/log/containers/haproxy/haproxy.log