Created attachment 670984 [details] NetworkName Description of problem: In webadmin the entity name is"Logical Network" And in History DB / Reports this entity fields are called only "Network" e.x "Network Name" In order to distinguish, and allow coralation between Webadmin & Reports Version-Release number of selected component (if applicable): 3.1/si25.2 How reproducible: always Steps to Reproduce: 1.Examine Engine DB table "network" the field name is "Network Name" 2.Examine Engine DB "vds_interface" the field name is "Network Name" 3.Examine History DB "v3_1_host_interface_configuration_view" the field name is "Network Name" 4.Examine in Webadmin under cluster, See Logical Networks Tab name of entity is "Logical Network" Actual results: field name is "Network Name" Expected results: Should change to "Logical Network Name" Additional info:
Verified on oVirt 3.5 Alpha 1: bash-4.1$ psql -d engine -c "select table_name, column_name from information_schema.columns where table_name like '%dwh%view%' and column_name like '%network%';" table_name | column_name -----------------------------------------------+---------------------- dwh_host_interface_configuration_history_view | logical_network_name dwh_vm_interface_configuration_history_view | logical_network_name bash-4.1$ psql -d ovirt_engine_history -c "select table_name, column_name from information_schema.columns where table_name like 'v3_5%configuration%' and column_name like '%network%';" table_name | column_name ---------------------------------------------+---------------------- v3_5_configuration_history_hosts_interfaces | logical_network_name v3_5_latest_configuration_hosts_interfaces | logical_network_name v3_5_configuration_history_vms_interfaces | logical_network_name v3_5_latest_configuration_vms_interfaces | logical_network_name
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://rhn.redhat.com/errata/RHEA-2015-0177.html