Bug 1805275 - Report information on bare metal systems about system manufacturer and product info
Summary: Report information on bare metal systems about system manufacturer and produc...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.5.0
Assignee: Clayton Coleman
QA Contact: Junqi Zhao
Depends On:
Blocks: 1804012
TreeView+ depends on / blocked
Reported: 2020-02-20 15:40 UTC by Clayton Coleman
Modified: 2020-07-13 17:16 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1804012
Last Closed: 2020-07-13 17:16:23 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:16:48 UTC

Description Clayton Coleman 2020-02-20 15:40:33 UTC
+++ This bug was initially created as a clone of Bug #1804012 +++

In order to better support bare metal deployments, clusters under telemetry should report a subset of system information for each node, including bios, system, and baseboard manufacturer and product names.  Summarize that in virt_platform reported back.

The cardinality of this metric might be higher on bare metal clusters, but in general larger clusters have significantly fewer hardware sets than nodes.

Comment 1 Clayton Coleman 2020-02-20 15:42:44 UTC
Merged into 4.5, should be available in those builds.

Comment 3 Clayton Coleman 2020-02-24 17:10:54 UTC
Should be ready for verification (I see this data in telemetry already).  Please verify in CI builds if OCP is still waiting.

Comment 7 errata-xmlrpc 2020-07-13 17:16:23 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.


Note You need to log in before you can comment on or make changes to this bug.