Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1416509 - [3.4] 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 ...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Command Line Interface (Show other bugs)
3.4.0
Unspecified Unspecified
high Severity medium
: ---
: 3.4.z
Assigned To: Fabiano Franz
Xingxing Xia
:
: 1416512 (view as bug list)
Depends On: 1279303
Blocks: 1414414
  Show dependency treegraph
 
Reported: 2017-01-25 11:27 EST by Fabiano Franz
Modified: 2017-02-10 12:00 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
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).
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-01-31 15:20:12 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0218 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4.1.2 bug fix update 2017-01-31 20:18:20 EST

  None (edit)
Description Fabiano Franz 2017-01-25 11:27:56 EST
Bug opened to track the backport of the bug below to 3.4.x:

https://bugzilla.redhat.com/show_bug.cgi?id=1279303
Comment 2 Scott Dodson 2017-01-25 11:36:55 EST
*** Bug 1416512 has been marked as a duplicate of this bug. ***
Comment 4 Johnny Liu 2017-01-26 00:08:24 EST
Verified this bug with atomic-openshift-3.4.1.2-1.git.0.d760092.el7.x86_64, and PASS.

# oc get nodes --selector="registry=enabled"|wc -l
59

# oadm manage-node --selector="registry=enabled" --schedulable=false
NAME                               STATUS                     AGE
qe-jialiu-node-registry-router-1   Ready,SchedulingDisabled   2h
qe-jialiu-node-registry-router-10   Ready,SchedulingDisabled   2h
qe-jialiu-node-registry-router-11   Ready,SchedulingDisabled   2h
...
qe-jialiu-node-registry-router-8   Ready,SchedulingDisabled   2h
qe-jialiu-node-registry-router-9   Ready,SchedulingDisabled   2h

# oadm manage-node --selector="registry=enabled" --schedulable=true
NAME                               STATUS    AGE
qe-jialiu-node-registry-router-1   Ready     2h
qe-jialiu-node-registry-router-10   Ready     2h
qe-jialiu-node-registry-router-11   Ready     2h
...
qe-jialiu-node-registry-router-8   Ready     2h
qe-jialiu-node-registry-router-9   Ready     2h
Comment 6 errata-xmlrpc 2017-01-31 15:20:12 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:0218

Note You need to log in before you can comment on or make changes to this bug.