Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1255638

Summary: [dialog] support unicode output
Product: [oVirt] otopi Reporter: David Jaša <djasa>
Component: Plugins.dialogAssignee: Yaniv Kaul <ykaul>
Status: CLOSED CURRENTRELEASE QA Contact: Gonza <grafuls>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: bazulay, bugs, combuster, djasa, dougsland, gklein, lsurette, oourfali, pstehlik, Rhev-m-bugs, yeylon, ykaul
Target Milestone: ovirt-3.6.0-rcFlags: rule-engine: ovirt-3.6.0+
ylavi: planning_ack+
rule-engine: devel_ack+
pstehlik: testing_ack+
Target Release: 1.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Unicode character within otopi human dialog caused error during string processing. Consequence: In most cases unicode string could not be accepted. Fix: Modify the method otopi process input and log to accept unicode string correctly. Result: User can enter unicode text.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-10 12:51:30 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:    
Bug Blocks: 1262550    

Description David Jaša 2015-08-21 08:56:11 UTC 
Description of problem:
unicode in e.g. surname makes ovirt-engine-extension-aaa-ldap-setup crash on Search during Setup validation

Version-Release number of selected component (if applicable):
ovirt-engine-extension-aaa-ldap-setup-1.1.0-0.0.master.el6ev.noarch / RHEV 3.6.0-10

How reproducible:
always

Steps to Reproduce:
1. add a domain with unicode-formatted names using -setup command
2. in Setup Validation phase, perform a search for such a name with unicode in the name
3.

Actual results:
[ ERROR ] Failed to execute stage 'Setup validation': 'ascii' codec can't encode character u'\u0161' in position 65: ordinal not in range(128)

Expected results:
search completes successfully

Additional info:
only -setup command is affected, the users work in engine correctly when the domain is added using configuration files manually
Comment 1 Alon Bar-Lev 2015-08-21 09:00:47 UTC 
please stop opening downstream bugs for a component/issue that is not downstream specific.
Comment 2 Alon Bar-Lev 2015-08-21 09:01:34 UTC 
setup log, please.
Comment 5 Alon Bar-Lev 2015-08-21 16:09:05 UTC 
this is interesting how we did not see this before, probably most people use plain ascii.
Comment 6 Alon Bar-Lev 2015-08-29 16:58:13 UTC 
*** Bug 1257047 has been marked as a duplicate of this bug. ***
Comment 7 Ivan Bulatovic 2015-09-15 23:15:56 UTC 
*** Bug 1263160 has been marked as a duplicate of this bug. ***
Comment 9 Gonza 2016-01-28 09:30:14 UTC 
Verified with:
ovirt-engine-extension-aaa-ldap-setup-1.1.2-1.el6.noarch

...
2016-01-28 10:26:57 INFO    AAA_AUTHZ_PRINCIPAL_NAME: my_test
2016-01-28 10:26:57 INFO    AAA_AUTHZ_PRINCIPAL_FIRST_NAME: Čeněk
...