Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1773243

Summary: Cannot identify cluster virtualization or bare metal status from telemetry
Product: OpenShift Container Platform Reporter: Clayton Coleman <ccoleman>
Component: MonitoringAssignee: Clayton Coleman <ccoleman>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: alegrand, anpicker, crawford, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1773246 (view as bug list) Environment:
Last Closed: 2020-01-23 11:13:05 UTC Type: Bug
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:    
Bug Blocks: 1773246    

Description Clayton Coleman 2019-11-16 21:38:14 UTC
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 5 Alex Crawford 2019-11-22 18:05:35 UTC
Verified that I can view the virtualization(s) in use by cluster.

Comment 7 errata-xmlrpc 2020-01-23 11:13:05 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-2020:0062