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:
I swear this has been reported already but I didn't see an open bug, so it might be a regression....?
Attempting to create a repo with a multibyte name fails. Clicking create once gives a spinner and then the Add Repo button is mysteriously re-enabled. Clicking it once more gives a notification that it was successful, but browsing the repo tree shows no repo.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create a new provider and product.
2. Within the product, attempt to create a repo, 饺子.
3. Hit the Add Repository button; view results.
4. Hit the Add Repository button a second time; view results.
5. Expand the product tree
Actual results:
* The first time it is clicked, the button is disabled, the spinner appears, and then the button is re-enabled. User is given no notification.
* The second time it is clicked, the user is given a notification that it was successfully created, but expanding the tree shows no such repo
Expected results:
Valid creation and/or notification and/or rejection of possibly invalid (??) repo names.
Additional info: