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.
Systems with localized names resulted in errors when registering in System Engine. An error in the candlepin component prevented special characters from being used as the system name. This fix updates the candlepin option to allow any characters in system name.
Description of problem:
Although we can rename an existing system already registered to katello to one using multibyte characters, manual creation throws an error when trying to use such characters.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Using subscription-manager, register a system to katello
2. Systems > $system > System Properties
3. Edit the Name field and replace the existing name with "红豆"; verify this works.
4. Systems > +New System
5. Attempt to create a new system with the name "不好"
6. View results.
Actual results:
* System name cannot contain most special characters.
* System not created
Expected results:
* Parity with the ability to rename an existing system.
Additional info:
Workaround: create system using standard alphanumeric characters ("buhao") and then edit that system to replace the name with multibyte ("不好"), per steps 1-3 above.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2012-1543.html
Description of problem: Although we can rename an existing system already registered to katello to one using multibyte characters, manual creation throws an error when trying to use such characters. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Using subscription-manager, register a system to katello 2. Systems > $system > System Properties 3. Edit the Name field and replace the existing name with "红豆"; verify this works. 4. Systems > +New System 5. Attempt to create a new system with the name "不好" 6. View results. Actual results: * System name cannot contain most special characters. * System not created Expected results: * Parity with the ability to rename an existing system. Additional info: Workaround: create system using standard alphanumeric characters ("buhao") and then edit that system to replace the name with multibyte ("不好"), per steps 1-3 above.