diff --git a/puppet/services/pacemaker.yaml b/puppet/services/pacemaker.yaml
index 3e88415f1b..f524622dc9 100644
--- a/puppet/services/pacemaker.yaml
+++ b/puppet/services/pacemaker.yaml
@@ -115,6 +115,9 @@ outputs:
           resource-stickiness: { value: INFINITY }
         corosync_token_timeout: 10000
         pacemaker::corosync::settle_tries: {get_param: CorosyncSettleTries}
+        pacemaker::resource::bundle::deep_compare: true
+        pacemaker::resource::ip::deep_compare: true
+        pacemaker::resource::ocf::deep_compare: true
         tripleo.pacemaker.firewall_rules:
           '130 pacemaker tcp':
             proto: 'tcp'
diff --git a/releasenotes/notes/update-pcmk-resource-by-default-ed54100721f55a30.yaml b/releasenotes/notes/update-pcmk-resource-by-default-ed54100721f55a30.yaml
new file mode 100644
index 0000000000..808058c947
--- /dev/null
+++ b/releasenotes/notes/update-pcmk-resource-by-default-ed54100721f55a30.yaml
@@ -0,0 +1,8 @@
+---
+fixes:
+  - |
+    Historically if a puppet definition for a pacemaker resource did change
+    puppet would not update it. We now enable the updating of pacemaker resources
+    by default. The main use case being restarting a bundle when a bind mount gets
+    added. Puppet will wait for the resource to completely restart before
+    proceeding with the deploy.