Previously, attempting to use the "pcs resource update" command to change the "remote-node" attribute failed even if the target resource already had "remote-node" configured with the same value as the new one. This caused failures in a variety of Puppet operations that automatically update node information. Now, the pcs utility is capable of changing "remote-node" in the described circumstances, which prevents the problem from occurring.
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:0866
Created attachment 1339614 [details] proposed fix