Bug 955507 - Provider, product an repository are inconsistent regarding accepting i18n chars in name field
Summary: Provider, product an repository are inconsistent regarding accepting i18n cha...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On: 952639
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-23 08:02 UTC by Adam Saleh
Modified: 2014-07-02 14:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 952639
Environment:
Last Closed: 2014-07-02 14:09:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Adam Saleh 2013-04-23 08:02:36 UTC
Description of problem:

It was my impression, that every "object" in katello has a name,
that allows i18n characters, and label that allows only alphanumerics for compatiblity with pulp/yum backends.

Right now, situation looks like this:

Custom provider form
  doesn't have label
  alphanumerics-only constraint is enforced on its name.

Custom product form
  has label field
  alphanumeric-only constraint is enforced on its name
  when trying to supply name \w i18n chars, valid label is created (include Ext::LabelFromName), but creation is forbidden

Custom repo form
  has label field
  there are no constraints on name (I can create repository with name Русский, or 洪)
  valid label is automaticaly created, if containing i18n chars, by hashing

Expected results:

According to test-cases

https://tcms.engineering.redhat.com/case/211097, 
https://tcms.engineering.redhat.com/case/181838

provider, product and repo names should accept i18n names.

Katello Version: 1.4.1-1.git.151.5330760.el6

Comment 1 Tom McKay 2013-07-03 15:32:42 UTC
Created custom provider and products named: 来惊喜

Comment 2 Bryan Kearney 2014-07-02 14:09:35 UTC
This was delivered with 6.0.3, which is the Satellite 6 Beta.


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