Bug 1415554

Summary:	[infrastructure_public_271] PodNodeSelector related validation issue
Product:	OpenShift Container Platform	Reporter:	DeShuai Ma <dma>
Component:	Node	Assignee:	Seth Jennings <sjenning>
Status:	CLOSED WONTFIX	QA Contact:	Xiaoli Tian <xtian>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.5.0	CC:	aos-bugs, decarr, gblomqui, jokerman, mmccomas, wmeng
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-03 18:04:56 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:

Description DeShuai Ma 2017-01-23 03:18:21 UTC

Description of problem:
Test PodNodeSelector on ocp-3.5, still have the same issue with upstream, using this bug to trace upstream PodNodeSelector related issue, just in case we forget it.

https://github.com/kubernetes/kubernetes/issues/35505
https://github.com/kubernetes/kubernetes/issues/35506

Version-Release number of selected component (if applicable):
openshift v3.5.0.7+390ef18
kubernetes v1.5.2+43a9be4
etcd 3.1.0-rc.0

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Avesh Agarwal 2017-01-23 14:04:09 UTC

I have PRs in flight to address these issues in kube upstream:

https://github.com/kubernetes/kubernetes/pull/35554
https://github.com/kubernetes/kubernetes/pull/36395

Comment 2 Derek Carr 2017-01-31 22:57:01 UTC

Reducing priority as this is not a release blocker.

Will review related PRs though.

Comment 5 Greg Blomquist 2019-07-03 18:04:56 UTC

Discussion in upstream PRs indicates that we're not likely to implement this.