we want to add new panel to Hosts Inventory Dashboard with data about the host hardware. In order to see for each host the: -hardware_manufacturer (Server Manufacturer) -hardware_product_name (Server Name) -hardware_serial_number (Server Serial Number) -host_type (Host / Hypervisor)
Functionally-wise it's verified (ovirt-engine-4.4.5.7-0.1.el8ev.noarch ovirt-engine-dwh-4.4.5.4-1.el8ev.noarch). The Hosts HW Details table shows all the data (Host Name, CPU Model, Number of CPUs, Memory Size, Server Manufacturer, Server Name, Server Serial Number). But I found a possible regression regarding to bug 1914825 where all the views should be updated from v4_3 to v4_4. The panel current query is using view v4_3_configuration_history_hosts: SELECT DISTINCT CASE WHEN delete_date IS NULL THEN host_name WHEN delete_date IS NOT NULL THEN host_name || ' (Removed on ' || CAST ( CAST ( delete_date AS date ) AS varchar ) || ')' END AS host_name, cpu_model, number_of_cores AS host_cpu, ROUND ( CAST ( COALESCE ( memory_size_mb, 0.00 ) AS float ) :: numeric / 1024, 1 ) AS host_memsize, hardware_manufacturer AS "Server Manufacturer", hardware_product_name AS "Server Name", hardware_serial_number AS "Server Serial Number" FROM v4_4_configuration_history_hosts WHERE host_id IN ($host_id) AND history_id IN ( SELECT MAX (history_id) FROM v4_3_configuration_history_hosts GROUP BY host_id ) AND CASE WHEN '$show_deleted'='Yes' THEN 1=1 WHEN '$show_deleted'='No' THEN delete_date isnull END ORDER BY host_name, hardware_manufacturer, hardware_product_name @Aviv: if the v4_3 view is intentional, then this RFE is verified. If not, I don't mind to verify this bug anyway and the view name can be fixed in a separate bug.
Hi Pavel Thanks for notice that. the v4_3 view is not intentional. you can verify this bug and the view name will be fixed in a separate bug. Thanks
The view name fixed in this patch: https://gerrit.ovirt.org/#/c/ovirt-dwh/+/113755/
All right, then moving to VERIFIED.
This bugzilla is included in oVirt 4.4.5 release, published on March 18th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.5 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.