Bug 886559

Summary: Luci does not handle UTF-8 inputs correctly
Product: Red Hat Enterprise Linux 6 Reporter: Jaroslav Kortus <jkortus>
Component: luciAssignee: Ryan McCabe <rmccabe>
Status: CLOSED DUPLICATE QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: low    
Version: 6.4CC: cluster-maint, rsteiger
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-12 14:53:50 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 Jaroslav Kortus 2012-12-12 14:51:35 UTC
Description of problem:
Following actions do not work with UTF-8 chars:
1. Creating and editing resource name (in Resources tab). Luci confirms the action, but nothing is performed, no new resource appears or it's still the same as before the editation.

2. Creating service name (in Service Groups). This operation also reports "green bar", but no service group is created. Other operations (disable for instance) behave the same way, green bar, but no action taken.

3. Editing service with resource that has UTF characters in it's name. This fails like this: Error adding resource type "apache": 'resourcename'. I used apache resource in this case, manually entered in cluster.conf.

Although it may not seem ideal to use non-ascii characters in cluster resources or services, cluster stack supports it well and just luci is not processing it correctly.

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

How reproducible:
always

Steps to Reproduce:
1. create resource with UTF-8 chars (tested with apache resource named "čččč")
2. create cluster service with resource from (1)
3. create cluster service with UTF-8 chars in it's name
4. perform operations on resource (rename) and service (stop, disable, restart)
  
Actual results:
actions failing or (worse) reporting false success, while nothing is really performed on cluster (it also does not appear in UI after reloading the page)

Expected results:
it should work with UTF-8 chars the same way as with normal ascii chars.

Additional info:

Comment 1 Radek Steiger 2012-12-12 14:53:50 UTC

*** This bug has been marked as a duplicate of bug 880358 ***