Bug 1685952
| Summary: | sync daemonset should tolerate taints (3.10) | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Sebastian Mossberg <smossber> | |
| Component: | Installer | Assignee: | Vadim Rutkovsky <vrutkovs> | |
| Installer sub component: | openshift-ansible | QA Contact: | Siva Reddy <schituku> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | unspecified | |||
| Priority: | unspecified | CC: | aos-bugs, gpei, jdesousa, jialiu, jokerman, jupierce, mmccomas, schituku, smossber, vrutkovs, wmeng | |
| Version: | 3.10.0 | |||
| Target Milestone: | --- | |||
| Target Release: | 3.10.z | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| 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
|
Story Points: | --- | |
| Clone Of: | 1635462 | |||
| : | 1690200 (view as bug list) | Environment: | ||
| Last Closed: | 2019-06-11 09:30:48 UTC | Type: | --- | |
| 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: | 1635462 | |||
| Bug Blocks: | 1690200 | |||
|
Comment 2
Vadim Rutkovsky
2019-03-06 11:59:53 UTC
*** Bug 1685960 has been marked as a duplicate of this bug. *** Bug for logging team to evaluate fluentd https://bugzilla.redhat.com/show_bug.cgi?id=1685970 Fix is available in openshift-ansible-3.10.123-1 The sync daemon sets are tolerating the taints put on the node.
Version:
oc v3.10
openshift v3.10
openshift-ansible-3.10.124-1.git.0.0bed46f.el7.noarch.rpm
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
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-2019:0786 |