+++ This bug was initially created as a clone of Bug #1857507 +++ Description of problem: when a node enabled for SR-IOV is tainted, sriov-device-plugin pods are not able to get scheduled on to the node therefore preventing pods requiring SR-IOV from getting scheduled. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.taint node that has SR-IOV enabled e.g. oc adm taint node worker-21 worker=load-balancer:NoSchedule 2.reboot the node 3.sriov-device-plugin does not get scheduled on to the node Actual results: Expected results: sriov-device-plugin get scheduled onto the node Additional info: sriov-device-plugin tolerations: tolerations: - effect: NoSchedule key: node-role.kubernetes.io/master operator: Exists - effect: NoExecute key: node.kubernetes.io/not-ready operator: Exists - effect: NoExecute key: node.kubernetes.io/unreachable operator: Exists - effect: NoSchedule key: node.kubernetes.io/disk-pressure operator: Exists - effect: NoSchedule key: node.kubernetes.io/memory-pressure operator: Exists - effect: NoSchedule key: node.kubernetes.io/pid-pressure operator: Exists - effect: NoSchedule key: node.kubernetes.io/unschedulable operator: Exists - effect: NoSchedule key: node.kubernetes.io/network-unavailable operator: Exists These will not allow the pod to be scheduled. The other sriov pods have an additional toleration: tolerations: - operator: Exists That allows them to get scheduled.
*** Bug 1857509 has been marked as a duplicate of this bug. ***
Verified this bug on 4.5.0-202007172106.p0 oc rsh sriov-network-operator-54df58fd7b-hdv4g sh-4.2#cat bindata/manifests/plugins/sriov-device-plugin.yaml | grep toler -A 3 tolerations: - operator: Exists serviceAccountName: sriov-device-plugin containers:
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:2956