Back to bug 1299348
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Ken Gaillot | 2016-01-18 15:48:51 UTC | Status | NEW | MODIFIED |
| errata-xmlrpc | 2016-01-18 16:51:50 UTC | Status | MODIFIED | ON_QA |
| Ken Gaillot | 2016-01-18 18:29:33 UTC | Fixed In Version | pacemaker-1.1.13-10.el7_2.1 | |
| Martin Juricek | 2016-01-25 17:21:52 UTC | CC | mjuricek | |
| Martin Juricek | 2016-01-26 11:43:13 UTC | Flags | needinfo?(kgaillot) | |
| Ken Gaillot | 2016-01-26 16:25:40 UTC | Flags | needinfo?(kgaillot) | needinfo?(mjuricek) |
| Martin Juricek | 2016-01-26 17:30:46 UTC | Flags | needinfo?(mjuricek) | |
| Ken Gaillot | 2016-01-27 00:44:52 UTC | Fixed In Version | pacemaker-1.1.13-10.el7_2.1 | pacemaker-1.1.13-10.el7_2.2 |
| Martin Juricek | 2016-01-28 10:03:58 UTC | Status | ON_QA | VERIFIED |
| Ken Gaillot | 2016-02-09 17:23:46 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 | ||
| Milan Navratil | 2016-02-12 09:42:17 UTC | CC | mnavrati | |
| 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. | The pacemaker_remote service can now be stopped on an active Pacemaker Remote node, and the cluster gracefully migrates resources off the node before stopping the node. Previously, Pacemaker Remote nodes had to be taken out of the cluster before stopping the pacemaker_remote service, either explicitly or implicitly by commands such as "yum update", otherwise the node was fenced. Now, software upgrades and other routine maintenance are significantly easier to perform on Pacemaker Remote nodes. Note that all nodes in the cluster must be upgraded to a version supporting this feature before the feature can be used on any node. | ||
| errata-xmlrpc | 2016-02-16 00:25:20 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-02-16 11:18:20 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-02-16 06:18:20 UTC |
Back to bug 1299348