Back to bug 1416509
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Fabiano Franz | 2017-01-25 16:29:33 UTC | Priority | unspecified | high |
| Status | NEW | MODIFIED | ||
| Target Release | --- | 3.4.1 | ||
| Fabiano Franz | 2017-01-25 16:36:44 UTC | Doc Text | Cause: race condition when updating a batch of nodes (we verified the issue on 8+ nodes) to (un)schedulable with "oadm manage-node --schedulable=<true|false>". Consequence: several nodes couldn't be updated with the "object has been modified" error. Fix: use a patch on the "unschedulable" field of the node object instead of a full update. Result: all nodes could be properly updated schedulable and/or unschedulable (tested on a 60 nodes cluster). | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Scott Dodson | 2017-01-25 16:36:55 UTC | CC | sdodson | |
| errata-xmlrpc | 2017-01-25 16:37:48 UTC | Status | MODIFIED | ON_QA |
| Scott Dodson | 2017-01-25 16:38:28 UTC | Depends On | 1279303 | |
| Scott Dodson | 2017-01-25 16:39:10 UTC | Summary | Race condition is seen when updating a batch of nodes in cluster using "oadm manage-node" | [3.4] Race condition is seen when updating a batch of nodes in cluster using "oadm manage-node" |
| Johnny Liu | 2017-01-26 05:08:24 UTC | Status | ON_QA | VERIFIED |
| CC | jialiu | |||
| errata-xmlrpc | 2017-01-31 17:50:19 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2017-01-31 20:20:12 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-01-31 15:20:12 UTC | |||
| John Matthews | 2017-02-10 17:00:12 UTC | Blocks | 1414414 |
Back to bug 1416509