*** Bug 1846857 has been marked as a duplicate of this bug. ***
Issue is fixed with 4.4.0-0.nightly-2020-06-27-171816
# oc -n openshift-monitoring get pod -o wide | grep node-exporter
node-exporter-ddwpk 2/2 Running 0 93m 10.0.198.116 ip-10-0-198-116.us-east-2.compute.internal <none> <none>
node-exporter-fwjsq 2/2 Running 0 93m 10.0.178.102 ip-10-0-178-102.us-east-2.compute.internal <none> <none>
node-exporter-g5t76 2/2 Running 0 97m 10.0.209.148 ip-10-0-209-148.us-east-2.compute.internal <none> <none>
node-exporter-kxlj2 2/2 Running 0 97m 10.0.158.126 ip-10-0-158-126.us-east-2.compute.internal <none> <none>
node-exporter-spckf 2/2 Running 0 97m 10.0.163.150 ip-10-0-163-150.us-east-2.compute.internal <none> <none>
node-exporter-t2rc5 2/2 Running 0 93m 10.0.144.133 ip-10-0-144-133.us-east-2.compute.internal <none> <none>
# oc -n openshift-monitoring exec -c node-exporter node-exporter-ddwpk -- cat /var/node_exporter/textfile/virt.prom
# HELP virt_platform reports one series per detected virtualization type. If no type is detected, the type is "none".
# TYPE virt_platform gauge
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.