Bug 1308826
Summary: | [platformmanagement_public_596]Daemonset can't create pod on node which is unschedulable | ||
---|---|---|---|
Product: | OKD | Reporter: | DeShuai Ma <dma> |
Component: | Pod | Assignee: | Paul Weil <pweil> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | DeShuai Ma <dma> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.x | CC: | agoldste, aos-bugs, mmccomas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-19 13:54:21 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
2016-02-16 08:52:38 UTC
2 things: 1) There is no need to specify a spec.selector in this instance. However, if you do, you need to use the "new" format: spec: selector: matchLabels: name: hello-daemonset 2) This is currently working as implemented. See: https://github.com/kubernetes/kubernetes/issues/17297 https://github.com/kubernetes/kubernetes/pull/17318 https://github.com/kubernetes/kubernetes/issues/15310 Note, ultimately, the plan is to be able to have daemon sets place pods on unschedulable nodes. I would keep this New until upstream resolves the TODO and makes this work the way it's supposed to. Andy, this bug have fixed on latest ose, could help set on_qa? thanks. Test on openshift v3.2.0.6, it can schedule pod on node which is unschedulable verify this bug. |