Bug 1773246

Summary:	Cannot identify cluster virtualization or bare metal status from telemetry
Product:	OpenShift Container Platform	Reporter:	Clayton Coleman <ccoleman>
Component:	Monitoring	Assignee:	Clayton Coleman <ccoleman>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.z	CC:	alegrand, anpicker, erooth, juzhao, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone:	---
Target Release:	4.2.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1773243	Environment:
Last Closed:	2019-12-20 00:46:48 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1773243
Bug Blocks:

Description Clayton Coleman 2019-11-16 21:55:06 UTC

+++ This bug was initially created as a clone of Bug #1773243 +++

The cloud provider infrastructure type does not tell the whole story for what sort of deployment is in play. Since it is very important for triage and remote health monitoring to know the difference between bare metal, virt with no cloud provider, virt with cloud provider, or mismatched cloud provider and virt platform, we should introduce a metric that captures the virt type of a node and report it via telemetry.

Metric will be virt_platform{type="baremetal|xen|kvm|..."}, and reported per cluster as count of nodes with a given virt type. A node may have multiple virt types.

Use the standard package 'virt-what' to capture this metric in the node_exporter.

Should be backported to 4.2 to enable better support.

Comment 4 errata-xmlrpc 2019-12-20 00:46:48 UTC

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:4181