Description of problem: Search engine uses the following views : vdc_users vds vms and their corresponding versions that includes tag information : vdc_users_with_tags vds_with_tags vms_with_tags The result set returned by a view and its corresponding tag support versions should be similar except of fields that are related to the tag support itself. However, along the time there were some fields that are not related to tags and are omitted from the view or its corresponding tag support version Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.compare the attached no_tags.txt output that lists the columns of vdc_users, vds, vms views with with_tags.txt that lists teh corresponding vdc_users_with_tags, vds_with_tags, vms_with_tags with a tool like meld 2. 3. Actual results: Some columns that are not related to tags are omitted Expected results: Result set should be similar except columns related to tag support Additional info: the "*_with_tags" views are used only from the search engine that generates dynamic sql , therefor we should insure that the result sets are the same up to tag support in order to prevent searching for columns that are not exists in the view
Created attachment 1712581 [details] views without tag information
Created attachment 1712582 [details] views with tag information
The following are list of fields that exists in one view and missing from its corresponding tag support version and vise versa. each such field should be investigated and added to the relevant view if needed vdc_users : ========== external_id namespace vdc_users_with_tags : ====================== mla_role vm_guid vm_pool_name vds : ====== cluster_gluster_service cluster_virt_service enable_balloon gluster_peer_status hbas host_provider_id hw_manufacturer is_hosted_engine_host kernel_cmdline kernel_features last_stored_kernel_cmdline openstack_network_provider_id recoverable reinstall_required sshkeyfingerprint supported_emulated_machines vds_spm_priority vds_with_tags : ================= storage_id vms : ======= changed_fields cpu_pinning db_generation guest_agent_nics_hash hash host_cpu_flags is_run_once iso_path last_watchdog_action last_watchdog_event migration_support origin predefined_properties provider_id quota_enforcement_type transparent_hugepages trusted_service userdefined_properties volatile_run vms_with_tags : ================= storage_id
Here is the full list of changes that should be applied : Legend : ========= + This field is in regular view and is missing in the view that includes tag support and can be added without any risk - This field is in the view that supports tag and is missing from the regular view because it is part of the tag support * This field is in regular view and is missing in the view that includes tag support but will not be added for a reason (adding JOIN/S for example) vdc_users : ========== external_id + namespace + vdc_users_with_tags : ====================== mla_role - vm_guid - vm_pool_name - vds : ====== cluster_gluster_service + cluster_virt_service + enable_balloon + gluster_peer_status * (need additional JOIN/S) hbas + host_provider_id + hw_manufacturer + is_hosted_engine_host * (need additional JOIN/S) kernel_cmdline + kernel_features + last_stored_kernel_cmdline + openstack_network_provider_id + recoverable + reinstall_required + sshkeyfingerprint + supported_emulated_machines + vds_spm_priority + vds_with_tags : ================= storage_id - vms : ======= changed_fields + cpu_pinning + db_generation + guest_agent_nics_hash + hash + host_cpu_flags + is_run_once + iso_path + last_watchdog_action + last_watchdog_event + migration_support + origin + predefined_properties + provider_id + quota_enforcement_type + transparent_hugepages + trusted_service + userdefined_properties + volatile_run + vms_with_tags : ================= storage_id -
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.3 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.