Back to bug 1299341
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Ken Gaillot | 2016-01-18 15:47:58 UTC | Status | NEW | MODIFIED |
| errata-xmlrpc | 2016-01-18 16:51:37 UTC | Status | MODIFIED | ON_QA |
| Martin Juricek | 2016-01-20 10:30:31 UTC | Status | ON_QA | VERIFIED |
| Ken Gaillot | 2016-02-09 17:12:54 UTC | Doc Text | Cause: If a user deletes an attribute from a fence device, Pacemaker's stonithd might mistakenly remove the entire device. Consequence: The cluster would no longer use the fence device. Fix: Stonithd now properly distinguishes attribute removals from device removals. Result: Deleting a fence device attribute will work as intended, without removing the device itself. |
|
| Milan Navratil | 2016-02-12 09:40:55 UTC | CC | mnavrati | |
| Doc Text | Cause: If a user deletes an attribute from a fence device, Pacemaker's stonithd might mistakenly remove the entire device. Consequence: The cluster would no longer use the fence device. Fix: Stonithd now properly distinguishes attribute removals from device removals. Result: Deleting a fence device attribute will work as intended, without removing the device itself. | Prior to this update, if a user deleted an attribute from a fence device, Pacemaker's stonithd service sometimes mistakenly removed the entire device. Consequently, the cluster would no longer use the fence device. The underlying source code has been modified to fix this bug, and stonithd now properly distinguishes attribute removals from device removals. As a result, deleting a fence device attribute no longer removes the device itself. | ||
| errata-xmlrpc | 2016-02-16 00:25:37 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-02-16 11:18:03 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-02-16 06:18:03 UTC |
Back to bug 1299341