Bug 1379636
| Summary: | can not change node schedulable with oadm | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Wenkai Shi <weshi> |
| Component: | oc | Assignee: | Maru Newby <mnewby> |
| Status: | CLOSED ERRATA | QA Contact: | Xingxing Xia <xxia> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.4.0 | CC: | aos-bugs, bbennett, jokerman, mifiedle, mmccomas, tdawson, wabouham |
| Target Milestone: | --- | ||
| Target Release: | 3.4.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: |
no doc update
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-18 12:41:41 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: | |||
|
Description
Wenkai Shi
2016-09-27 09:28:01 UTC
The installer is unable to set the masters unschedulable as well. One workaround was to use the command: kubectl patch nodes <node-ip> -p '{"spec": {"unschedulable": true}}'
A fix was merged into origin master, see the linked github pull request. This has been merged into ose and is in OSE v3.4.0.12 or newer. It fixed in this version. [root@ansible ~]# rpm -qa | grep openshift-ansible ... openshift-ansible-3.4.9-1.git.0.94af651.el7.noarch ... [root@master ~]# openshift version openshift v3.4.0.12 kubernetes v1.4.0+776c994 etcd 3.1.0-alpha.1 [root@master ~]# oc get nodes NAME STATUS AGE node1.example.com Ready 24m master.example.com Ready,SchedulingDisabled 24m node2.example.com Ready 24m [root@master ~]# oadm manage-node master.example.com --schedulable=true NAME STATUS AGE master.example.com Ready 28m [root@master ~]# oadm manage-node master.example.com --schedulable=false NAME STATUS AGE master.example.com Ready,SchedulingDisabled 29m Does this bug require doc text or target release? afaik this was caught before release. Maru: Target release - yes. Doc text - no. Just set the type to 'no doc update' 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:0066 |