Bug 1797880

Summary:	Taint and Tolerations with BuildOverride not working as expected
Product:	OpenShift Container Platform	Reporter:	Rahul Rajendran <rpalathi>
Component:	Node	Assignee:	Michael Burke <mburke>
Status:	CLOSED ERRATA	QA Contact:	Weinan Liu <weinliu>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.11.0	CC:	aos-bugs, erich, harpatil, jokerman, mburke, nagrawal, rphillips
Target Milestone:	---	Flags:	rpalathi: needinfo+ rpalathi: needinfo+ rpalathi: needinfo+
Target Release:	3.11.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1837093 (view as bug list)		Environment:
Last Closed:	2020-06-17 20:21:25 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:
Bug Depends On:
Bug Blocks:	1837093

Description Rahul Rajendran 2020-02-04 06:20:26 UTC

Description of problem:

To schedule build pods in dedicated nodes, the buildOverride parameter in the master-config.yaml is appended with tolerations and a node is tainted with respective kay value pair. After initializing the build the pod seems to schedule on random node even it is appended with toleration values.

Version-Release number of selected component (if applicable):


How reproducible:

100%

Steps to Reproduce:

1. Edit the master-config.yaml and in the buildoverrides section define the   necessary tolerations. Restart the master api and controllers.

2. Taint a node with matching key-value pair.

3. Try launching a new application and observe on which node the build pod is running

Actual results:

The `build pod` gets scheduled on random node irrespective of the configuration

Expected results:

The `build pod` should be scheduled on a tainted node matching the toleration of the pod.

Additional info:

The same configuration is working fine if `nodeSelector` variable is used instead of `taint-toleration`.

Comment 1 Ryan Phillips 2020-02-06 15:10:41 UTC

Can you add the master-config.yaml you are using?

Comment 4 Rahul Rajendran 2020-02-11 09:37:34 UTC

Any progress on the issue?

Comment 12 Michael Burke 2020-05-18 19:53:41 UTC

**Updated docs PR number**

https://github.com/openshift/openshift-docs/pull/22242

Comment 13 Harshal Patil 2020-05-25 06:54:29 UTC

Thanks Michael.

Comment 17 Weinan Liu 2020-06-09 15:52:32 UTC

The updates look good to me

Comment 19 errata-xmlrpc 2020-06-17 20:21:25 UTC

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-2020:2477