Back to bug 1297564

Who When What Removed Added
Ken Gaillot 2016-01-11 21:41:14 UTC Priority urgent high
Status NEW POST
Target Release --- 6.8
Ken Gaillot 2016-01-13 19:35:07 UTC Status POST MODIFIED
errata-xmlrpc 2016-01-15 12:22:47 UTC Status MODIFIED ON_QA
Klaus Wenninger 2016-01-19 06:24:19 UTC CC kwenning
Fixed In Version pacemaker-1.1.14-1.1.el6
Klaus Wenninger 2016-01-29 15:12:37 UTC Fixed In Version pacemaker-1.1.14-1.1.el6 pacemaker-1.1.14-2.0.el6
Ken Gaillot 2016-02-09 17:23:52 UTC Doc Text Feature: The pacemaker_remote service may now be stopped on an active Pacemaker Remote node, and the cluster will gracefully migrate resources off the node before stopping the node.

Reason: Previously, Pacemaker Remote nodes had to be explicitly taken out of the cluster before stopping the pacemaker_remote service (whether explicitly, or implicitly by commands such as "yum update"), otherwise the node would be fenced.

Result: Software upgrades and other routine maintenance are now much easier to perform on Pacemaker Remote nodes.

Special note: All nodes in the cluster must be upgraded to a version supporting this feature before it can be used on any node.
Doc Type Bug Fix Enhancement
Ken Gaillot 2016-02-26 16:14:30 UTC Doc Text Feature: The pacemaker_remote service may now be stopped on an active Pacemaker Remote node, and the cluster will gracefully migrate resources off the node before stopping the node.

Reason: Previously, Pacemaker Remote nodes had to be explicitly taken out of the cluster before stopping the pacemaker_remote service (whether explicitly, or implicitly by commands such as "yum update"), otherwise the node would be fenced.

Result: Software upgrades and other routine maintenance are now much easier to perform on Pacemaker Remote nodes.

Special note: All nodes in the cluster must be upgraded to a version supporting this feature before it can be used on any node.
Feature: If the pacemaker_remote service is stopped on an active Pacemaker Remote node, the cluster will gracefully migrate resources off the node before stopping the node.

Reason: Previously, Pacemaker Remote nodes would be fenced when the service was stopped (including by commands such as "yum update"), unless the node was first explicitly taken out of the cluster.

Result: Software upgrades and other routine maintenance are now much easier to perform on Pacemaker Remote nodes.

Special note: All nodes in the cluster must be upgraded to a version supporting this feature before it can be used on any node.
Doc Type Enhancement Release Note
Lenka Špačková 2016-02-29 16:36:21 UTC Docs Contact slevine
Steven J. Levine 2016-03-01 20:18:47 UTC Doc Text Feature: If the pacemaker_remote service is stopped on an active Pacemaker Remote node, the cluster will gracefully migrate resources off the node before stopping the node.

Reason: Previously, Pacemaker Remote nodes would be fenced when the service was stopped (including by commands such as "yum update"), unless the node was first explicitly taken out of the cluster.

Result: Software upgrades and other routine maintenance are now much easier to perform on Pacemaker Remote nodes.

Special note: All nodes in the cluster must be upgraded to a version supporting this feature before it can be used on any node.
Graceful migration of resources when the `pacemaker_remote` service is stopped on an active Pacemaker Remote node

If the pacemaker_remote service is stopped on an active Pacemaker Remote node, the cluster will gracefully migrate resources off the node before stopping the node. Previously, Pacemaker Remote nodes would be fenced when the service was stopped (including by commands such as "yum update"), unless the node was first explicitly taken out of the cluster. Software upgrades and other routine maintenance procedures are now much easier to perform on Pacemaker Remote nodes.

Special note: All nodes in the cluster must be upgraded to a version supporting this feature before it can be used on any node.
Lenka Špačková 2016-03-02 08:16:31 UTC Doc Text Graceful migration of resources when the `pacemaker_remote` service is stopped on an active Pacemaker Remote node

If the pacemaker_remote service is stopped on an active Pacemaker Remote node, the cluster will gracefully migrate resources off the node before stopping the node. Previously, Pacemaker Remote nodes would be fenced when the service was stopped (including by commands such as "yum update"), unless the node was first explicitly taken out of the cluster. Software upgrades and other routine maintenance procedures are now much easier to perform on Pacemaker Remote nodes.

Special note: All nodes in the cluster must be upgraded to a version supporting this feature before it can be used on any node.
Graceful migration of resources when the *pacemaker_remote* service is stopped on an active Pacemaker Remote node

If the *pacemaker_remote* service is stopped on an active Pacemaker Remote node, the cluster will gracefully migrate resources off the node before stopping the node. Previously, Pacemaker Remote nodes were fenced when the service was stopped (including by commands such as "yum update"), unless the node was first explicitly taken out of the cluster. Software upgrades and other routine maintenance procedures are now much easier to perform on Pacemaker Remote nodes.

Note: All nodes in the cluster must be upgraded to a version supporting this feature before it can be used on any node.
Jaroslav Kortus 2016-03-17 21:12:11 UTC Status ON_QA ASSIGNED
Ken Gaillot 2016-03-18 17:38:26 UTC Status ASSIGNED POST
Tom Lavigne 2016-03-18 18:44:40 UTC CC tlavigne
Ken Gaillot 2016-03-18 19:19:16 UTC Status POST MODIFIED
Fixed In Version pacemaker-1.1.14-2.0.el6 pacemaker-1.1.14-5.el6
errata-xmlrpc 2016-03-18 19:29:35 UTC Status MODIFIED ON_QA
Jaroslav Kortus 2016-04-01 14:34:47 UTC Status ON_QA VERIFIED
CC slevine
Flags needinfo?(slevine)
Steven J. Levine 2016-04-01 15:30:41 UTC Flags needinfo?(slevine)
Steven J. Levine 2016-04-01 16:15:09 UTC Blocks 1323259
Steven J. Levine 2016-04-07 20:36:45 UTC Blocks 1325009
errata-xmlrpc 2016-05-09 18:29:22 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-05-10 23:52:33 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-05-10 19:52:33 UTC
Jan Pokorný [poki] 2016-10-24 13:36:11 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=1388102

Back to bug 1297564