Verified, #test for new package: (undercloud) [stack@undercloud-0 ~]$ ansible overcloud -b -mshell -a 'rpm -qa|grep puppet-pacemaker' compute-1 | SUCCESS | rc=0 >> puppet-pacemaker-0.7.2-0.20181008172518.9a4bc2d.el7ost.noarch compute-0 | SUCCESS | rc=0 >> puppet-pacemaker-0.7.2-0.20181008172518.9a4bc2d.el7ost.noarch controller-2 | SUCCESS | rc=0 >> puppet-pacemaker-0.7.2-0.20181008172518.9a4bc2d.el7ost.noarch controller-0 | SUCCESS | rc=0 >> puppet-pacemaker-0.7.2-0.20181008172518.9a4bc2d.el7ost.noarch controller-1 | SUCCESS | rc=0 >> puppet-pacemaker-0.7.2-0.20181008172518.9a4bc2d.el7ost.noarch #test for new reconnect_interval existance and defaults: (undercloud) [stack@undercloud-0 ~]$ ansible controller-0 -b -mshell -a 'pcs resource show overcloud-novacomputeiha-0|grep reconnect' [WARNING]: Found both group and host with same name: undercloud controller-0 | SUCCESS | rc=0 >> Attributes: reconnect_interval=60 server=172.17.1.16 (undercloud) [stack@undercloud-0 ~]$ ansible controller-0 -b -mshell -a 'pcs resource show overcloud-novacomputeiha-1|grep reconnect' [WARNING]: Found both group and host with same name: undercloud controller-0 | SUCCESS | rc=0 >> Attributes: reconnect_interval=60 server=172.17.1.12 #doctext is present at : https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/high_availability_add-on_reference/pacemaker_remote
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, 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-2018:3587