Red Hat Bugzilla – Bug 1379636
can not change node schedulable with oadm
Last modified: 2017-01-18 07:41:41 EST
Description of problem: Can not change node schedulable with oadm, there is no "PUT" seen from --loglevel=6 while change schedulable, but in oc 3.3 there is "PUT". Version-Release number of selected component (if applicable): atomic-openshift 3.4.0.3 openshift-ansible 3.4.2 How reproducible: 100% Steps to Reproduce: [root@openshift-129 ~]# oc get nodes master.example.com Ready 38m node1.example.com Ready 38m node2.example.com Ready 38m [root@openshift-129 ~]# oadm manage-node master.example.com --schedulable=false --loglevel=6 ... I0927 04:56:23.510042 20210 round_trippers.go:318] GET https://master.example.com:8443/api/v1/nodes/master.example.com 200 OK in 3 milliseconds NAME STATUS AGE master.example.com Ready 39m Actual results: Schedulable didn't change Expected results: Schedulable should be change to "SchedulingDisabled"
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