The column agent_ip has changed name, we require to fix analyzer for recent db (4.2). Generating reports: =================== psql:/usr/share/ovirt-log-collector/analyzer/produceReport/sqls/hosts_query_all.sql:137: ERROR: column v.agent_ip does not exist LINE 8: v.agent_ip AS "Agent IP", ^ QUERY: ( SELECT v.vds_name AS "Name of Host", CASE WHEN sp.spm_vds_id=v.vds_id THEN 'SPM' ELSE 'Normal' END AS "SPM", coalesce(htt.text, 'Unknown (id='||v.vds_type||')') AS "Host Type", c.name AS "Cluster", sp.name AS "Data Center", v.agent_ip AS "Agent IP", v.host_name AS "FQDN or IP", regexp_replace(v.rpm_version, '[a-z]+.', '') AS "vdsm", v.kvm_version AS "qemu-kvm", regexp_replace(v.libvirt_version, '[a-z]+.', '') AS "libvirt", v.spice_version AS "spice", v.kernel_version AS "kernel", hst.text AS "Status", v.host_os AS "Operating System", v.vm_count AS "VM Count", v.mem_available AS "Available memory (MB)", v.usage_mem_percent AS "Used memory %", v.usage_cpu_percent AS "CPU load %" FROM vds v JOIN cluster c ON c.cluster_id=v.cluster_id LEFT OUTER JOIN storage_pool sp ON c.storage_pool_id = sp.id LEFT OUTER JOIN host_status_temp hst ON hst.id = v.status LEFT OUTER JOIN host_type_temp htt ON htt.id = v.vds_type ORDER BY c.name, v.vds_name ) CONTEXT: PL/pgSQL function __temp_hosts_show_all() line 20 at RETURN QUERY Generated analyzer_report.html
Just a hint from: inventory_report/produceReport/sqls/hosts_query_all.sql -- We might have cases where engine db's like 3.2, 3.3, 3.4, 3.5 have -- vds table with column ip and 3.6 or later with column agent_ip. -- -- To avoid a second SQL query when going to compat mode let's -- change the column name in our own local temp. db. IF EXISTS (SELECT column_name FROM information_schema.columns WHERE table_name='vds' and column_name='ip') THEN ALTER TABLE vds RENAME COLUMN ip TO agent_ip; END IF;
Please make sure you don't break compatibility with 3.x which is the main use case of the analyzer right now.
Verified on version ovirt-log-collector-analyzer-4.2.4-3.el7ev.noarch
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 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.