Red Hat Bugzilla – Bug 961100
[RFE] Foreman should use an organization/environment name instead of label when displaying information in the UI
Last modified: 2017-02-13 10:54:05 EST
Created attachment 745387 [details]
Description of problem:
Foreman displays organization's labels (my guess to handle i18n?) in the UI for orgs and environments. That works fine but if the organization name or environment name created via katello have i18n characters, then their respective labels become a massive GUID. When you search for your organization in Foreman, it is really hard to know which organization to select (see attached screenshot).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install katello and foreman side by side
2. Using the Katello UI, create the Organization "São Paulo" with default environment "Amanhã"
3. Login to Foreman UI and select the appropriate page to see Organizations or Environments
The name of the organization is made up of "KT_" and a GUID
The name of the organization displayed should be KT_São Paulo or something similar
This is default katello behaviour: if an entity's name is not ascii, its label will be uuid, rather than the name with spaces substituted by "_"s. The user should specify an ascii label in such a case.
I don't agree with the resolution. This is a major usability issue
OK, so I spoke to Og a bit more about this and came up with a feature request for Foreman:
We need to get the interaction between Katello and Foreman as smooth, clean and user friendly as possible. One of these issues would be making sure our objects are named clearly and support I18N charsets if possible.
If all names in Foreman require ASCII then Foreman, like Katello should consider a name/label scheme like we did in Katello. We could adjust our integration to instead name the Orgs & Environments in Foreman with the Name field in Katello but then also pop
We added this because various subsystems, like yum, required that objects be named with ASCII characters only. More information can be found here on our design:
Going to re-open this and propose for a future release where we can determine the best way to get Foreman and Katello using I18N object names+labels working well together.
(In reply to Mike McCune from comment #3)
> If all names in Foreman require ASCII then Foreman, like Katello should
> consider a name/label scheme like we did in Katello. We could adjust our
> integration to instead name the Orgs & Environments in Foreman with the Name
> field in Katello but then also pop
I don't think names do require ASCII generally. The only place I can think of that does leak into external systems is the environment name, which is shared with Puppet. We could use a name/label scheme for this, and have discussed doing so in the past. Definitely a valid RFE.