Right now, the monitoring interval is hardcoded to 10 seconds [0]. Under load, this can create extra stress and since the timeout has already been bumped, it makes sense to bump this interval to a higher value as a trade off between detecting a failure and stressing the service. After some discussion on IRC, 30 seconds could be reasonable. [0] https://github.com/openstack/puppet-tripleo/blob/15e21010a8a8594678afe385821ee804ec9e16c7/manifests/profile/pacemaker/ovn_dbs_bundle.pp#L211
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 (Red Hat OpenStack Platform 16.1.7 (Train) bug fix and enhancement advisory), 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-2021:3762