Description of problem: rhv-log-collector-analyzer reports wrong VMs in Windows VM(s) with incorrect timezone section because of different time zones format in vms_query_windows_vms_with_incorrect_timezone.sql vs sp_table_linux_aux_timezone_query.sql Version-Release number of selected component (if applicable): rhv-log-collector-analyzer-0.2.3-0.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. setup correct time zone - guest agent does not complain about time zone problem 2. run analyzer 3. VMs are reported as wrongly configured Actual results: VMs are reported as wrongly configured Expected results: Correct VMs list Additional info: Wrong report is due to ------------ WHERE time_zone NOT IN ( SELECT zone FROM timezone_temp ); ------------ where vm_static contains ------------ VM Name | Time Zone -------------------+------------------- test | FLE Standard Time test1 | FLE Standard Time but timezone_temp contains ------------ INSERT INTO timezone_temp VALUES ('Etc/GMT', '(GMT+00:00) GMT Standard Time'), ('Europe/Kiev', '(GMT+02:00) FLE Standard Time'), ------------
Users can work around editing /usr/share/rhv-log-collector-analyzer/analyzer/produceReport/sqls/vms_query_windows_vms_with_incorrect_timezone.sql Replace: SELECT zone FROM timezone_temp With: SELECT zone FROM timezone_windows_temp
Can't verify due to this bz 1658509, please retarget milestone and remove from errata, thanks.
Steps: 1. Setup correct timezone 2. Run analyzer Result: No error messages in the analyzer report about wrongly configured VMs. Verified in: rhv-log-collector-analyzer-0.2.9-0.el7ev.noarch ovirt-engine-4.3.6.2-0.1.el7.noarch
sync2jira
Can this be closed current release for 4.3.6?
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of CURRENT RELEASE. 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://access.redhat.com/errata/RHBA-2019:3012