Back to bug 1646347
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Ken Gaillot | 2018-11-06 01:17:30 UTC | Status | NEW | POST |
| Target Release | --- | 7.6 | ||
| Doc Text | Cause: Pacemaker now verifies a node has resource information for a resource before synthesizing an internal result for an action on that resource. Consequence: This uncovered a pre-existing bug where clone notify actions on a Pacemaker Remote node would be routed through the wrong cluster node when the Pacemaker Remote connection is moving, causing the cluster to indefinitely loop trying to move the connection. Fix: Notify actions are now routed through the proper cluster node when a Pacemaker Remote connection is moving. Result: Notify actions are completed successfully, and the Pacemaker Remote connection is able to move successfully. | |||
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Chris Jones | 2018-11-06 13:30:57 UTC | Keywords | Triaged | |
| Ken Gaillot | 2018-11-07 21:30:21 UTC | Status | POST | MODIFIED |
| Fixed In Version | pacemaker-1.1.19-8.el7_6.1 | |||
| errata-xmlrpc | 2018-11-07 22:38:33 UTC | Status | MODIFIED | ON_QA |
| Ken Gaillot | 2018-11-07 22:42:47 UTC | CC | ctowsley | |
| Martin Juricek | 2018-11-08 10:01:18 UTC | CC | mjuricek | |
| QA Contact | cluster-qe | mkrcmari | ||
| Marian Krcmarik | 2018-11-12 16:16:57 UTC | Status | ON_QA | VERIFIED |
| Cole Towsley | 2018-11-19 18:13:24 UTC | Link ID | Red Hat Knowledge Base (Solution) 3703011 | |
| Lucie Vařáková | 2018-11-22 15:28:11 UTC | CC | lmanasko | |
| Doc Text | Cause: Pacemaker now verifies a node has resource information for a resource before synthesizing an internal result for an action on that resource. Consequence: This uncovered a pre-existing bug where clone notify actions on a Pacemaker Remote node would be routed through the wrong cluster node when the Pacemaker Remote connection is moving, causing the cluster to indefinitely loop trying to move the connection. Fix: Notify actions are now routed through the proper cluster node when a Pacemaker Remote connection is moving. Result: Notify actions are completed successfully, and the Pacemaker Remote connection is able to move successfully. | Previously, cloned notify actions on the Pacemaker Remote node were routed through the wrong cluster node when the Pacemaker Remote node was moving. As a consequence, the cluster looped indefinitely when trying to move the connection. With this update, notify actions are now routed through a proper cluster node when the Pacemaker Remote connection is moving. As a result, the describer problem no longer occurs. | ||
| errata-xmlrpc | 2018-11-26 00:03:19 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2018-11-27 01:21:58 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2018-11-26 20:21:58 UTC | |||
| errata-xmlrpc | 2018-11-27 01:22:11 UTC | Link ID | Red Hat Product Errata RHBA-2018:3667 | |
| Ken Gaillot | 2018-11-29 15:22:44 UTC | CC | autobot-eus-copy | |
| Ken Gaillot | 2021-01-06 21:17:25 UTC | CC | nwahl |
Back to bug 1646347