Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1685952 - sync daemonset should tolerate taints (3.10)
Summary: sync daemonset should tolerate taints (3.10)
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.10.z
Assignee: Vadim Rutkovsky
QA Contact: Siva Reddy
: 1685960 (view as bug list)
Depends On: 1635462
Blocks: 1690200
TreeView+ depends on / blocked
Reported: 2019-03-06 11:47 UTC by Sebastian Mossberg
Modified: 2019-03-19 01:33 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: sync daemonset didn't ignore tainted nodes Consequence: if some nodes were tainted, sync pods won't run there and reconcile the config Fix: sync DS pods now tolerate all taints Result: tainted nodes get configuration updated
Clone Of: 1635462
: 1690200 (view as bug list)
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Comment 2 Vadim Rutkovsky 2019-03-06 11:59:53 UTC
Created 3.10 PR

Comment 3 Scott Dodson 2019-03-06 13:33:35 UTC
*** Bug 1685960 has been marked as a duplicate of this bug. ***

Comment 4 Scott Dodson 2019-03-06 13:35:19 UTC
Bug for logging team to evaluate fluentd

Comment 5 Vadim Rutkovsky 2019-03-08 11:53:51 UTC
Fix is available in openshift-ansible-3.10.123-1

Comment 7 Siva Reddy 2019-03-19 01:30:53 UTC
The sync daemon sets are tolerating the taints put on the node.

oc v3.10
openshift v3.10


Steps to reproduce:
1. taint the node
   # oc adm taint node $node NodeWithImpairedVolumes=true:NoExecute
    #oc describe node $node | grep -i taint
2. delete the sync pod ds and recreate it
   # oc get ds sync -o yaml > sync-ds.yaml
   # oc delete ds sync
   # oc create -f sync-ds.yaml
3. Note the sync pods

    The sync pods get created with out any issue in spite of taint being present on the node.Note that the logging pods are still affected by the taints

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