606d58caa3
Reason for this is that there are two functions to detect a change in a pcmk resource: - pacemaker_restart_resource? -> which parses crm_simulate and was necessary due to https://bugzilla.redhat.com/show_bug.cgi?id=1561617 (Fixed in pacemaker-1.1.18-12) - pacemaker_restart_resource_ng? -> which is the preferred one and uses crm_diff xml output (and is a lot simpler). We can remove pacemaker_restart_resource? fully now that newton and Centos 7 are unsupported. Tested as follows: - Deployed a fresh Train overcloud w/ this change - Ran a redeployment forcing a config change on an HA bundle - Ran another redeployment forcing a CIB change on an HA bundle OVNDBSPacemakerMonitorIntervalSlave: 666 observed that the bundle was restarted correctly: [root@controller-0 ~]# pcs resource config ovn-dbs-bundle |grep 666 monitor interval=666s role=Slave timeout=60s (ovndb_servers-monitor-interval-666s) - Also tested in CI via https://review.opendev.org/c/openstack/tripleo-heat-templates/+/803101 Change-Id: Iba736839ae12f3adf180b53cd7fc5c552d03bd47 |
||
|---|---|---|
| .. | ||
| facter | ||
| pacemaker | ||
| puppet | ||
| serverspec/type | ||
| tools | ||