Back to bug 1327469
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Jiri Stransky | 2016-04-15 08:56:23 UTC | CC | jstransk | |
| Fabio Massimo Di Nitto | 2016-06-16 08:41:52 UTC | Priority | high | urgent |
| CC | fdinitto | |||
| Severity | high | urgent | ||
| Andrew Beekhof | 2016-06-17 00:37:42 UTC | Status | NEW | ASSIGNED |
| Andrew Beekhof | 2016-06-17 01:24:05 UTC | Status | ASSIGNED | POST |
| Ken Gaillot | 2016-06-17 19:55:06 UTC | Target Release | --- | 7.3 |
| Dean Jansa | 2016-06-22 19:34:28 UTC | CC | djansa | |
| Chris Feist | 2016-06-22 19:37:20 UTC | CC | cfeist | |
| John Ruemker | 2016-06-23 13:41:01 UTC | CC | jruemker | |
| Flags | needinfo?(abeekhof) | |||
| Marcel Kolaja | 2016-06-23 14:26:14 UTC | Blocks | 1349493 | |
| Marcel Kolaja | 2016-06-23 14:26:46 UTC | Keywords | ZStream | |
| Ken Gaillot | 2016-06-23 15:46:30 UTC | Status | POST | MODIFIED |
| Fixed In Version | pacemaker-1.1.15-3.el7 | |||
| errata-xmlrpc | 2016-06-23 16:01:18 UTC | Status | MODIFIED | ON_QA |
| Andrew Beekhof | 2016-06-23 23:52:59 UTC | Flags | needinfo?(abeekhof) | |
| Ken Gaillot | 2016-07-05 19:41:51 UTC | Doc Text | Cause: Pacemaker might schedule actions that depend on an unrunnable action on a cloned resource. Consequence: Log files would be noisier, and "crm_resource --wait" would never return, due to the scheduled actions. There is no significant effect on the cluster itself, due to the cluster not proceeding beyond the unrunnable action. Fix: Pacemaker now correctly does not schedule actions that depend on an unrunnable clone action. Result: Log files are cleaner, and "crm_resource --wait" returns as usual when the cluster stabilizes. |
|
| Patrik Hagara | 2016-08-22 12:06:22 UTC | Status | ON_QA | VERIFIED |
| CC | phagara | |||
| Milan Navratil | 2016-10-17 17:08:05 UTC | CC | mnavrati | |
| Docs Contact | mnavrati | |||
| Doc Text | Cause: Pacemaker might schedule actions that depend on an unrunnable action on a cloned resource. Consequence: Log files would be noisier, and "crm_resource --wait" would never return, due to the scheduled actions. There is no significant effect on the cluster itself, due to the cluster not proceeding beyond the unrunnable action. Fix: Pacemaker now correctly does not schedule actions that depend on an unrunnable clone action. Result: Log files are cleaner, and "crm_resource --wait" returns as usual when the cluster stabilizes. | The "crm_resource --wait" command and a "pcs" command with the "--wait" option no work correctly Previously, *Pacemaker* sometimes scheduled actions that depended on an unrunnable action on a cloned resource. As a consequence, log files became unnecessarily verbose, and the "crm_resource --wait" command never returned due to the scheduled actions. There was no significant effect on the cluster itself, as the cluster did not proceed beyond the unrunnable action. Now, *Pacemaker* no longer schedules actions that depend on an unrunnable clone action. As a result, log files are cleaner, and running "crm_resource --wait" or a "pcs" command with the "--wait" option returns as expected when the cluster stabilizes. |
||
| errata-xmlrpc | 2016-11-02 09:38:14 UTC | Status | VERIFIED | RELEASE_PENDING |
| Milan Navratil | 2016-11-02 11:09:46 UTC | Doc Text | The "crm_resource --wait" command and a "pcs" command with the "--wait" option no work correctly Previously, *Pacemaker* sometimes scheduled actions that depended on an unrunnable action on a cloned resource. As a consequence, log files became unnecessarily verbose, and the "crm_resource --wait" command never returned due to the scheduled actions. There was no significant effect on the cluster itself, as the cluster did not proceed beyond the unrunnable action. Now, *Pacemaker* no longer schedules actions that depend on an unrunnable clone action. As a result, log files are cleaner, and running "crm_resource --wait" or a "pcs" command with the "--wait" option returns as expected when the cluster stabilizes. | The "crm_resource --wait" command and a "pcs" command with the "--wait" option now work correctly Previously, *Pacemaker* sometimes scheduled actions that depended on an unrunnable action on a cloned resource. As a consequence, log files became unnecessarily verbose, and the "crm_resource --wait" command never returned due to the scheduled actions. There was no significant effect on the cluster itself, as the cluster did not proceed beyond the unrunnable action. Now, *Pacemaker* no longer schedules actions that depend on an unrunnable clone action. As a result, log files are cleaner, and running "crm_resource --wait" or a "pcs" command with the "--wait" option returns as expected when the cluster stabilizes. |
| errata-xmlrpc | 2016-11-03 18:59:12 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-11-03 14:59:12 UTC |
Back to bug 1327469