Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 880358

Summary: [RFE] luci unicode support
Product: Red Hat Enterprise Linux 6 Reporter: Radek Steiger <rsteiger>
Component: luciAssignee: Ryan McCabe <rmccabe>
Status: CLOSED WONTFIX QA Contact: cluster-qe <cluster-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.4CC: cfeist, cluster-maint, fdinitto, jkortus, jpokorny, tlavigne
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-21 22:31:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Radek Steiger 2012-11-26 19:40:58 UTC
Description of problem:

THe RHEL6 cluster itself is able to handle unicode characters in names and parameters just fine. Unicode characters like national ones are however not usable when managing the cluster from within luci - the communication part of luci is not able to handle them as seen in a traceback that appears anytime an attempt to use a unicode character is made (full log attached below):

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/luci/lib/ricci_communicator.py", line 328, in batch_run
    batch_xml = minidom.parseString(batch_xml_str).firstChild
  File "/usr/lib/python2.6/site-packages/_xmlplus/dom/minidom.py", line 1925, in parseString
    return expatbuilder.parseString(string)
  File "/usr/lib/python2.6/site-packages/_xmlplus/dom/expatbuilder.py", line 942, in parseString
    return builder.parseString(string)
  File "/usr/lib/python2.6/site-packages/_xmlplus/dom/expatbuilder.py", line 223, in parseString
    parser.Parse(string, True)
UnicodeEncodeError: 'ascii' codec can't encode characters in position 765-766: ordinal not in range(128)


Version-Release number of selected component (if applicable):
luci-0.26.0-26.el6.i686


How reproducible:
Always


Steps to Reproduce:
1. Create a cluster
2. Try to add a fence device/resource/service with a name or parameter containing unicode characters

  
Actual results:
The action is reported as successful but no fence device/resource/service has been really added to the cluster configuration. Luci log contains error messages.


Expected results:
Changes are applied successfully.


Additional info:
Luci sections affected:
 - fence device name / parameters
 - failover domain name
 - resource name / parameters
 - service name (including resources name / parameters)
 - cluster configuration options

Comment 2 Radek Steiger 2012-11-28 18:21:45 UTC
Another questionable place that has got issues with unicode characters is the nodelist. In this case however I'm not sure if a usage of unicode characters inside a hostname is something that is/should be supported.

Comment 3 Radek Steiger 2012-12-12 14:53:56 UTC
*** Bug 886559 has been marked as a duplicate of this bug. ***