Description of problem:
All node-exporter pods are pending:
$ oc get pods -l app.kubernetes.io/component=exporter -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-state-metrics-669dbd4d69-4wrtw 3/3 Running 0 53m 10.131.8.27 ip-10-0-53-237.us-west-2.compute.internal <none> <none>
node-exporter-4qjv9 0/2 Pending 0 18h <none> <none> <none> <none>
node-exporter-5cvxk 0/2 Pending 0 18h <none> <none> <none> <none>
Warning FailedScheduling 3m11s default-scheduler 0/12 nodes are available: 1 node(s) didn't have free ports for the requested pod ports, 11 node(s) didn't match Pod's node affinity/selector.
events. Happened during 4.7.21 -> 4.8.2 upgrade on vSphere build cluster
This is also related to https://github.com/openshift/cluster-monitoring-operator/pull/1257#pullrequestreview-700719930
Setting severity/priority to high since it is preventing a CI cluster upgrade.
checked with recent 4.8 -> 4.9 nightly payload upgrade with azure cluster, did not see the reported error,
and search from CI upgrade jobs, no such error for node-exporter
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.