From 40d91a06a03e6e283cde747d80ad57e23bff6cb5 Mon Sep 17 00:00:00 2001 From: Michele Baldessari Date: Wed, 25 Nov 2020 19:05:04 +0100 Subject: [PATCH] Fix reconnect_interval on remotes with pcs 0.10 When switching to the pcs 0.10 providers we moved from the the general pcmk_resource provider to the pcmk_remote backend. While doing this we lost the ability to specify the reconnect_interval. Tested by deploying tripleo with the following: ExtraConfig: pacemaker_remote_reconnect_interval: 180 And correctly observing that the remotes have the right reconnect_interval: [root@controller-0 ~]# pcs resource config compute-0 |grep reconnect Attributes: reconnect_interval=180 server=172.17.1.96 Change-Id: Idb6e4ba4eadbeeb52b959bc688eb5e043f11c155 Closes-Bug: #1905606 --- lib/puppet/provider/pcmk_remote/default.rb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/lib/puppet/provider/pcmk_remote/default.rb b/lib/puppet/provider/pcmk_remote/default.rb index 3109c3b8..fc288bd0 100644 --- a/lib/puppet/provider/pcmk_remote/default.rb +++ b/lib/puppet/provider/pcmk_remote/default.rb @@ -28,6 +28,8 @@ Puppet::Type.type(:pcmk_remote).provide(:default) do if not_empty_string(@resource[:remote_address]) cmd += ' ' + @resource[:remote_address] end + # reconnect_interval always has a default + cmd += " reconnect_interval=#{@resource[:reconnect_interval]}" if not_empty_string(resource_params) cmd += ' ' + resource_params end