Description of problem: There is a problem which could lead to different problems. One of them I am reporting is the failure fetching information about hypervisors from API. An example error message: ERROR: Failure fetching information about hypervisors from API. Error (UnicodeDecodeError): 'ascii' codec can't decode byte 0xd0 in position 32204: ordinal not in range(128) ERROR: _get_hypervisors_from_api: 'ascii' codec can't decode byte 0xd0 in position 32204: ordinal not in range(128) The other possibility could be a failure with non-UTF8 files inside folders which are collected by the engine-log-collector. It looks like a regression because for engine-log-collector it was working. Version-Release number of selected component (if applicable): 4.1. How reproducible: always Steps to Reproduce: 1. put, for example, Cyrillic or German/French special characters to the "description" field for hypervisor 2. try to run: ovirt-log-collector (which is supposed to collect sosreports from RHV Hosts) Actual results: Failure and error message. Expected results: it is working in the same way as it used to work for engine-log-collector Additional info: It looks like the UnicodeDecodeError is the Python Exception which normally happens when decoding a string from a certain coding.
Handling unicode characters in Python SDKv4 should be fixed by BZ1461060 targeted to 4.1.5
Verified by following Steps to reproduce, ovirt-log-collector finishes without any error. python-ovirt-engine-sdk4-4.2.1-1.a3, ovirt-engine-4.2.0-0.0.master.20171108151837.
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/RHEA-2018:1478
BZ<2>Jira Resync
sync2jira