Comment 10 for bug 1978997

So the problem is reproduced if we downgrade only resource-agents.
 https://review.opendev.org/c/openstack/tripleo-common/+/846351
 https://zuul.opendev.org/t/openstack/build/72c725792946461f9a16760c6437fb8e

On the oher hand, it is not reproduced when we downgrade pacemaker/pacemaker_remote
 https://review.opendev.org/c/openstack/tripleo-common/+/846352
 https://zuul.opendev.org/t/openstack/build/eed22d317f0e4c67b358a5f308b036af

So this is likely the problem with pacemaker_remote (as pacemaker package is not used in the container)

Good
~~~
pacemaker.x86_64 2.1.2-4.el9 @quickstart-centos-highavailability
pacemaker-cli.x86_64 2.1.2-4.el9 @quickstart-centos-highavailability
pacemaker-cluster-libs.x86_64 2.1.2-4.el9 @quickstart-centos-highavailability
pacemaker-libs.x86_64 2.1.2-4.el9 @quickstart-centos-highavailability
pacemaker-remote.x86_64 2.1.2-4.el9 @quickstart-centos-highavailability
pacemaker-schemas.noarch 2.1.2-4.el9 @quickstart-centos-highavailability
~~~

Bad
~~~
pacemaker.x86_64 2.1.3-2.el9 @quickstart-centos-highavailability
pacemaker-cli.x86_64 2.1.3-2.el9 @quickstart-centos-highavailability
pacemaker-cluster-libs.x86_64 2.1.3-2.el9 @quickstart-centos-highavailability
pacemaker-libs.x86_64 2.1.3-2.el9 @quickstart-centos-highavailability
pacemaker-remote.x86_64 2.1.3-2.el9 @quickstart-centos-highavailability
pacemaker-schemas.noarch 2.1.3-2.el9 @quickstart-centos-highavailability
~~~
~~~