Bug 1466382
| Summary: | [RFE] add selector option to oadm cordon | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Sergi Jimenez Romero <sjr> |
| Component: | oc | Assignee: | Maciej Szulik <maszulik> |
| Status: | CLOSED ERRATA | QA Contact: | Xingxing Xia <xxia> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.5.0 | CC: | acomabon, aos-bugs, jokerman, maszulik, mmccomas, xiaocwan, yapei |
| Target Milestone: | --- | Flags: | maszulik:
needinfo-
|
| Target Release: | 3.9.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
Feature: new flag added to the `oc adm cordon` command to allow selecting nodes by label.
Reason: There was a need to be able to mark multiple nodes as "unschedulable", without having to perform the operation on each individual node.
Result: `oc adm cordon` now supports a "--selector" flag which results in all nodes matching a given label being marked as "unschedulable".
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-03-13 22:27:23 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
Sergi Jimenez Romero
2017-06-29 13:52:13 UTC
Upstream PR [1] has merged. Waiting on Origin PR. 1. https://github.com/kubernetes/kubernetes/pull/52917 Please move to ON_QA like bug 1466390, thanks Verified in v3.9.0-0.16.0 # oc get no --show-labels NAME STATUS ROLES AGE VERSION LABELS 172.16.120.129 Ready <none> 33m v1.9.0-beta1 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=172.16.120.129,registry=enabled,role=node,router=enabled 172.16.120.54 Ready,SchedulingDisabled <none> 34m v1.9.0-beta1 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=172.16.120.54,openshift-infra=apiserver,role=node # oc adm cordon -l role=node,router=enabled node "172.16.120.129" cordoned # oc get no --show-labels NAME STATUS ROLES AGE VERSION LABELS 172.16.120.129 Ready,SchedulingDisabled <none> 34m v1.9.0-beta1 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=172.16.120.129,registry=enabled,role=node,router=enabled 172.16.120.54 Ready,SchedulingDisabled <none> 35m v1.9.0-beta1 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=172.16.120.54,openshift-infra=apiserver,role=node # oc adm uncordon -l role=node,router=enabled node "172.16.120.129" uncordoned # oc get no --show-labels NAME STATUS ROLES AGE VERSION LABELS 172.16.120.129 Ready <none> 34m v1.9.0-beta1 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=172.16.120.129,registry=enabled,role=node,router=enabled 172.16.120.54 Ready,SchedulingDisabled <none> 35m v1.9.0-beta1 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=172.16.120.54,openshift-infra=apiserver,role=node 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:0403 |