Bug 729111
| Summary: | Some notifications not properly handling unicode characters | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Corey Welton <cwelton> |
| Component: | WebUI | Assignee: | Shannon Hughes <shughes> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Katello QA List <katello-qa-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 | CC: | mmccune |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-22 17:51:51 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: | 736791 | ||
| Bug Blocks: | 709813, 747354 | ||
this error is occuring because we have to url encode the restful call for DELETE actions. Candlepin can not lookup the org record since the actual key they are using does not match up with the Org/Owner. I need to discuss this with some of the CP devs to come up with a gameplan on how to handle. please retest. CP had to upgrade resteasy to fix this. I'm going to mark this verified. I can't repro anymore - I seem to be able to delete unicode orgs now. Can reopen if it appears again |
Description of problem: This might be a regression - I thought this was fixed at some point - but I'm seeing it rear its ugly head (again). Some notifications are rendering garbage when trying to display multibyte characters. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a new org called 你好. 2. Refresh orgs page (to assure it's actually there) 3. Attempt to delete Actual results: 404 Resource Not Found: {"displayMessage":"owner with key: ä½ å¥½ was not found."} Expected results: 404 Resource Not Found: {"displayMessage":"owner with key: 你好 was not found."} Generally speaking, notifications should be unicode-friendly. Additional info: I am going to make this block bug #709813 because I don't currently know of another way to test such a scenario. But we should try to get this fixed once and for all, across the notifications code. if I find this to actually be a dupe (i.e., the other was never fixed) i will close it.