Bug 1881594 - Not able to un-taint master nodes
Summary: Not able to un-taint master nodes
Keywords:
Status: CLOSED DUPLICATE of bug 1887519
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.0
Assignee: Ryan Phillips
QA Contact: Weinan Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-22 18:12 UTC by Anurag saxena
Modified: 2020-11-11 18:30 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-11 18:30:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Anurag saxena 2020-09-22 18:12:31 UTC
Description of problem:Not able to untaint master nodes on 4.6. Seems like we are able to do that on 4.5 though. Is this an expected behavior on 4.6?


Version-Release number of selected component (if applicable):4.6.0-0.nightly-2020-09-21-081745


How reproducible:Always


Steps to Reproduce:
1.oc adm taint node qe-anuragcp2-zgc59-master-0.c.openshift-qe.internal node-role.kubernetes.io/master-
2.
3.

Actual results: Taint still present after successful untaint

$ oc adm taint node qe-anuragcp2-zgc59-master-0.c.openshift-qe.internal node-role.kubernetes.io/master-
node/qe-anuragcp2-zgc59-master-0.c.openshift-qe.internal untainted

$ oc describe node/qe-anuragcp2-zgc59-master-0.c.openshift-qe.internal | grep -i taint
Taints:             node-role.kubernetes.io/master:NoSchedule



Expected results: Expecting master node to untaint successfuly


Additional info:

I0921 19:49:02.379720       1 node_controller.go:419] Pool master: node qe-anuragcp2-zgc59-master-0.c.openshift-qe.internal: changed annotation machineconfiguration.openshift.io/state = Done
I0921 19:49:02.379977       1 event.go:282] Event(v1.ObjectReference{Kind:"MachineConfigPool", Namespace:"", Name:"master", UID:"f2f3db79-3b07-448b-8816-3a63736b1b8f", APIVersion:"machineconfiguration.openshift.io/v1", ResourceVersion:"10656", FieldPath:""}): type: 'Normal' reason: 'AnnotationChange' Node qe-anuragcp2-zgc59-master-0.c.openshift-qe.internal now has machineconfiguration.openshift.io/currentConfig=rendered-master-ccbdbdec801726ae41e1bb0ca79db2d2
I0921 19:49:02.380024       1 event.go:282] Event(v1.ObjectReference{Kind:"MachineConfigPool", Namespace:"", Name:"master", UID:"f2f3db79-3b07-448b-8816-3a63736b1b8f", APIVersion:"machineconfiguration.openshift.io/v1", ResourceVersion:"10656", FieldPath:""}): type: 'Normal' reason: 'AnnotationChange' Node qe-anuragcp2-zgc59-master-0.c.openshift-qe.internal now has machineconfiguration.openshift.io/desiredConfig=rendered-master-ccbdbdec801726ae41e1bb0ca79db2d2
I0921 19:49:02.380065       1 event.go:282] Event(v1.ObjectReference{Kind:"MachineConfigPool", Namespace:"", Name:"master", UID:"f2f3db79-3b07-448b-8816-3a63736b1b8f", APIVersion:"machineconfiguration.openshift.io/v1", ResourceVersion:"10656", FieldPath:""}): type: 'Normal' reason: 'AnnotationChange' Node qe-anuragcp2-zgc59-master-0.c.openshift-qe.internal now has machineconfiguration.openshift.io/state=Done
I0921 19:49:07.381734       1 status.go:90] Pool master: All nodes are updated with rendered-master-ccbdbdec801726ae41e1bb0ca79db2d2

Comment 1 Seth Jennings 2020-09-22 18:30:07 UTC
Can you provide the following

oc get clusteroperators machine-config -oyaml
oc get machineconfigpools -oyaml

Comment 6 Ryan Phillips 2020-11-11 18:30:29 UTC

*** This bug has been marked as a duplicate of bug 1887519 ***


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