Bug 1023137

Summary: Config templates with multibyte characters result in poorly-used namespace
Product: Red Hat Satellite Reporter: Corey Welton <cwelton>
Component: ProvisioningAssignee: Ohad Levy <ohadlevy>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: NightlyCC: dcleal, skottler
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-25 13:17:11 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 Corey Welton 2013-10-24 17:18:21 UTC 
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 17:19:29 UTC 
Satellite-6.0.2-RHEL-6-20131023.1
Comment 3 Dominic Cleal 2013-10-25 13:17:11 UTC 
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 ***