Created attachment 1505784 [details] screen shot of virt-who config overview Description of problem: The following fields in the overview tab for a virt-who config should have the prefix removed: Satellite Virt Who Configure/Config|Hypervisor Type Satellite Virt Who Configure/Config|Hypervisor Server Satellite Virt Who Configure/Config|Hypervisor Username Satellite Virt Who Configure/Config|Interval Version-Release number of selected component (if applicable): 6.5 snap 3 How reproducible: always Steps to Reproduce: 1. Infrastructure -> Virt Who configurations -> Create config 2. After creating the config, see its overview. Actual results: Some fields in the overview are prefixed with "Satellite Virt Who Configure/Config" for example "Satellite Virt Who Configure/Config|Hypervisor Type" Expected results: Fields shouldn't have this prefix (ie "Hypervisor Type"). Additional info: See attached screenshot of overview tab
Seems like an issue with translations, bk you worked on extracting strings some time ago which seemed to fail because it pull also Katello strings, does it ring any bell? I don't see this in upstream.
@Marek look at this line from app/helpers/foreman_virt_who_configure/configs_helper.rb def config_attribute_default_label(attr) s_(ForemanVirtWhoConfigure::Config.gettext_translation_for_attribute_name(attr).titleize) end I believe the titleize should be on the outside, since the s_ seems to do the lookup and then split on the "|" character.
You're correct indeed, I'm confused why/how this worked before. Anyway, I'll send a fix. Thanks!
Created redmine issue https://projects.theforeman.org/issues/25776 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25776 has been resolved.
*** Bug 1708160 has been marked as a duplicate of this bug. ***
Verified fix in Sat 6.6 snap 2. Prefix has been removed from field names, see attachment 1568499 [details] for example
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. https://access.redhat.com/errata/RHSA-2019:3172