Back to bug 1416506

Who When What Removed Added
Fabiano Franz 2017-01-25 16:26:54 UTC Status NEW MODIFIED
Fabiano Franz 2017-01-25 16:27:10 UTC Priority unspecified medium
Fabiano Franz 2017-01-25 16:28:36 UTC Target Release --- 3.3.1
Fabiano Franz 2017-01-25 16:29:42 UTC Priority medium high
Fabiano Franz 2017-01-25 16:36:35 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:38:44 UTC Depends On 1279303
Scott Dodson 2017-01-25 16:39:17 UTC Summary Race condition is seen when updating a batch of nodes in cluster using "oadm manage-node" [3.3] Race condition is seen when updating a batch of nodes in cluster using "oadm manage-node"
errata-xmlrpc 2017-02-01 15:20:52 UTC Status MODIFIED ON_QA
Johnny Liu 2017-02-03 02:15:32 UTC CC jialiu
QA Contact xxia jialiu
Johnny Liu 2017-02-03 06:13:52 UTC Status ON_QA VERIFIED
errata-xmlrpc 2017-02-21 22:41:01 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2017-02-22 18:11:26 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2017-02-22 13:11:26 UTC

Back to bug 1416506