Description of problem: CNO only tolerates node.kubernetes.io/network-unavailable taint. In https://github.com/openshift/ovn-kubernetes/pull/671 we added the "k8s.ovn.org/network-unavailable" to block pod creations when ovnkube-node is down. We need to change the taint to be the official k8s one. - effect: NoSchedule key: node.kubernetes.io/network-unavailable operator: Exists 55s Warning FailedScheduling pod/network-operator-5697868476-vlqnv 0/27 nodes are available: 1 node(s) didn't match Pod's node affinity/selector, 1 node(s) had taint {role: workload}, that the pod didn't tolerate, 25 node(s) had taint {k8s.ovn.org/network-unavailable: }, that the pod didn't tolerate.
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759