Hi all, The just-released Pacemaker 2.0.0 and 1.1.19 releases have an issue when a Pacemaker Remote node is upgraded before the cluster nodes.
Pacemaker 2.0.0 contains a fix (also backported to 1.1.19) for the longstanding issue of "crm_node -n" getting the wrong name when run on the command line of a Pacemaker Remote node whose node name is different from its local hostname. However, the fix can cause resource agents running on a Pacemaker Remote node to hang when used with a cluster node older than 2.0.0 / 1.1.19. The only workaround is to upgrade all cluster nodes before upgrading any Pacemaker Remote nodes (which is the recommended practice anyway). -- Ken Gaillot <kgail...@redhat.com> _______________________________________________ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
