Description of problem: When running rhv-log-collector-analyzer --live, the section ' Check Non default Values in vdc_options' provides incorrect data: ~~~ WARNING #1 - 16.1. Check Non default Values in vdc_options The output in this section is clearly problematic: COPY ( — Licensed under the Apache License, Version 2.0 (the "License"); — you may not use this file except in compliance with the License. — You may obtain a copy of the License at — — http://www.apache.org/licenses/LICENSE-2.0 — — Unless required by applicable law or agreed to in writing, software — distributed under the License is distributed on an "AS IS" BASIS, — WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. — See the License for the specific language governing permissions and — limitations under the License. — SELECT optname AS "Option Name", optvalue AS "Option Value", defaultvalue AS "Default Value" FROM __temp_vdc_options_get_non_default_value() ORDER BY optname ) TO STDOUT WITH CSV DELIMITER E'|' HEADER Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/engine_db_query/init.py", line 283, in query_return_csv sys.stdout ProgrammingError: structure of query does not match function result type DETAIL: Returned type text does not match expected type character varying in column 2. CONTEXT: PL/pgSQL function __temp_vdc_options_get_non_default_value() line 6 at RETURN QUERY ~~~ Also 'VM(s) with unmanaged disks/interfaces' flags VM's that are using Unattended.xml as part of sysprep. Version-Release number of selected component (if applicable): rhv-log-collector-analyzer-0.2.4-0.el7ev.noarch rhvm 4.3.4 How reproducible: 100% Steps to Reproduce: 1. Run analyzer against a RHV 4.3.4 environment Actual results: The proper data should be reported back. Expected results: Incorrect data is being reported back. Additional info:
Thanks for the report. Already fixed in version 0.2.5-0 (or higher).
Verified on ovirt-engine-4.3.5.4-0.1.el7.noarch and rhv-log-collector-analyzer-0.2.10-0.el7ev.noarch
sync2jira
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://access.redhat.com/errata/RHBA-2019:3012