Could you provide sosreports? I may be able to see if I can tell what's going on from those.

Do we know if this worked in prior versions (i.e., was this configuration part of the QA setup before)?

(In reply to Martin Juricek from comment #4)
> But one strange thing can be observed /var/log/messages. The master score
> periodically changes from 2->1 and back 1->2:

Looks like a bug. If the monitor succeeds for the promoted node, OCF_CHECK_LEVEL is 0 (the default), and we're not read-only, then we set the promotion score to 1 and then to 2.

~~~
mysql_monitor() {
...
    if [ $OCF_CHECK_LEVEL -gt 0 -a -n "$OCF_RESKEY_test_table" ]; then
    ...
    else
        # In case no exnteded tests are enabled and we are in master/slave mode _always_ set the master score to 1 if we reached this point
        ocf_is_ms && $CRM_MASTER -v 1
    fi

    if ocf_is_ms && ! get_read_only; then
        ocf_log debug "MySQL monitor succeeded (master)";
        # Always set master score for the master
        $CRM_MASTER -v 2
        return $OCF_RUNNING_MASTER
    else
        ocf_log debug "MySQL monitor succeeded";
        return $OCF_SUCCESS
    fi
~~~

This results in two unnecessary attribute changes every time the monitor runs for a healthy promoted node.

https://github.com/ClusterLabs/resource-agents/pull/1850

Patch to fix demoted node score bouncing between ~3600 and 1:
https://github.com/ClusterLabs/resource-agents/pull/1874

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (resource-agents bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:6899