Bug 1416506
| Summary: | [3.3] Race condition is seen when updating a batch of nodes in cluster using "oadm manage-node" | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Fabiano Franz <ffranz> |
| Component: | oc | Assignee: | Fabiano Franz <ffranz> |
| Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.3.0 | CC: | aos-bugs, jialiu, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | 3.3.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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-02-22 18:11:26 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1279303 | ||
| Bug Blocks: | |||
|
Description
Fabiano Franz
2017-01-25 16:24:32 UTC
Verified this bug with atomic-openshift-3.3.1.12-1.git.0.3d14c02.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 1h qe-jialiu-node-registry-router-10 Ready,SchedulingDisabled 1h qe-jialiu-node-registry-router-11 Ready,SchedulingDisabled 1h <--snip--> qe-jialiu-node-registry-router-7 Ready,SchedulingDisabled 1h qe-jialiu-node-registry-router-8 Ready,SchedulingDisabled 1h qe-jialiu-node-registry-router-9 Ready,SchedulingDisabled 1h # oadm manage-node --selector="registry=enabled" --schedulable=true NAME STATUS AGE qe-jialiu-node-registry-router-1 Ready 1h qe-jialiu-node-registry-router-10 Ready 1h qe-jialiu-node-registry-router-11 Ready 1h <--snip--> qe-jialiu-node-registry-router-7 Ready 1h qe-jialiu-node-registry-router-8 Ready 1h qe-jialiu-node-registry-router-9 Ready 1h 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:0289 |