Bug 1477950

Summary:	sdk4 does not handle unicode data
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Olimp Bockowski <obockows>
Component:	ovirt-engine-sdk-python	Assignee:	Ondra Machacek <omachace>
Status:	CLOSED ERRATA	QA Contact:	Radim Hrazdil <rhrazdil>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	mgoldboi, mperina
Target Milestone:	ovirt-4.2.0	Keywords:	ZStream
Target Release:	---	Flags:	lsvaty: testing_plan_complete-
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	python-ovirt-engine-sdk4-4.1.6	Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:
Clones:	1479479 (view as bug list)		Environment:
Last Closed:	2018-05-15 17:34:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1461060
Bug Blocks:	1479479

Description Olimp Bockowski 2017-08-03 09:56:54 UTC

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.

Comment 3 Martin Perina 2017-08-03 12:55:06 UTC

Handling unicode characters in Python SDKv4 should be fixed by BZ1461060 targeted to 4.1.5

Comment 4 Radim Hrazdil 2017-11-16 13:52:40 UTC

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.

Comment 7 errata-xmlrpc 2018-05-15 17:34:51 UTC

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

Comment 8 Franta Kust 2019-05-16 13:05:44 UTC

BZ<2>Jira Resync

Comment 9 Daniel Gur 2019-08-28 12:57:50 UTC

sync2jira

Comment 10 Daniel Gur 2019-08-28 13:02:59 UTC

sync2jira

Comment 11 Daniel Gur 2019-08-28 13:13:04 UTC

sync2jira

Comment 12 Daniel Gur 2019-08-28 13:17:17 UTC

sync2jira