Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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: