Bug 1023137 - Config templates with multibyte characters result in poorly-used namespace
Config templates with multibyte characters result in poorly-used namespace
Status: CLOSED DUPLICATE of bug 1023062
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Provisioning (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified (vote)
: Unspecified
: --
Assigned To: Ohad Levy
Katello QA List
Depends On:
  Show dependency treegraph
Reported: 2013-10-24 13:18 EDT by Corey Welton
Modified: 2014-06-19 15:07 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-10-25 09:17:11 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Corey Welton 2013-10-24 13:18:21 EDT
Description of problem:
See also: bug #1023062

Similar to bug^^, when user creates a config template with multibyte characters, the resulting URL namespace does not include the template name in the URL

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. hammer -u admin -p admin template create --name 你好 --type snippet --file ~/foo.txt
2. hammer -u admin -p admin template create --name jalapeño --type snippet --file ~/foo.txt
3. hammer -u admin -p admin template create --name foobar --type snippet --file ~/foo.txt 
4. Nav to config templates in UI and view resulting URLs.

Actual results:
foobar gets '<id>-foobar' in URL
jalapeño gets '<id>-jalepeno' in URL (may or may not be ok, still not congruent with other parts of UI but whatev)
你好 gets '<id>-' in URL

Expected results:

Congruent handling of multibyte characters in object names across the UI

Additional info:
Comment 1 Corey Welton 2013-10-24 13:19:29 EDT
Comment 3 Dominic Cleal 2013-10-25 09:17:11 EDT
This is working as designed, but we'll fix the resources that aren't via bug #1023062.

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

Note You need to log in before you can comment on or make changes to this bug.