Bug 1563399
| Summary: | Pods cannot be scheduled in post-install namespaces without adding node-selector annotation to namespace | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Bill DeCoste <wdecoste> |
| Component: | Installer | Assignee: | Vadim Rutkovsky <vrutkovs> |
| Status: | CLOSED DUPLICATE | QA Contact: | Johnny Liu <jialiu> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.9.0 | CC: | aos-bugs, bleanhar, glamperi, jokerman, jwendell, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | 3.9.z | ||
| 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: | 2018-04-13 12:21:12 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
Bill DeCoste
2018-04-03 20:31:11 UTC
This is happening because we only label non master, non infra nodes as node-role.kubernetes.io/compute=true and then set the default node selector to match that. In the special case where all nodes are masters or all nodes are infra that's not going to work. I think we should special case those and apply the label 'node-role.kubernetes.io/compute=true' to the list of labels we set for the installer. Just to be clear, this is only happening because of the default atomic-openshift-installer behavior. This is not something production environments would ever hit. (In reply to Brenton Leanhardt from comment #2) > Just to be clear, this is only happening because of the default > atomic-openshift-installer behavior. This is not something production > environments would ever hit. Will it be fixed in OCP 3.9? Right now, a single Master/Node VM install is not an option. Bug 1567028 is same root cause, marking this as a dupe of that one as that bug and it's 3.10 counterpart already have a PR that's in progress. *** This bug has been marked as a duplicate of bug 1567028 *** |