Bug 536466 (RHQ-811)
| Summary: | Entering double-byte characters into affinity group name field results in garbage. | ||
|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Corey Welton <cwelton> |
| Component: | Core UI | Assignee: | RHQ Project Maintainer <rhq-maint> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 1.1pre | CC: | asantos, jshaughn |
| Target Milestone: | --- | Keywords: | SubBug |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://jira.rhq-project.org/browse/RHQ-811 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
Red Hat Enterprise Linux Server release 5.2 (Tikanga) Kernel \r on an \m Linux rlx-0-12.rhndev.redhat.com 2.6.18-92.1.10.el5 #1 SMP Wed Jul 23 03:55:54 EDT 2008 i686 i686 i386 GNU/Linux java version "1.5.0_16" Java(TM) 2 Runtime Environment, Standard Edit
|
|
| Last Closed: | 2014-05-02 17:55:49 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 536208 | ||
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-811 Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug making sure we're not missing any bugs in rhq_triage |
1. Administration > High Availability > "???admin.home.Ha.ListAffinityGroups???" 2. Create New 3. Enter a double-byte string ("北京")on the resulting page; hit the Create button [1] Expected results: Characters render Current results: Non-doublebyte garbage strings for the Affinity Group name. ("北京") Notes: Only mention this one because it was noted that doublebyte stuff is generally handled non-uniform across the system due to differing technologies being used. It was indicated, in some manner, that the older stuff was broken, but anything newly developed ought to work. That doesn't appear to be the case here. [1] if JIRA can't display the above doublebyte chars: * Go to http://www.xinhuanet.com/ and copy a few characters to paste into the field.