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.
Created attachment 1825385[details]
[1] Infrastructure - Virt-who Configurations - 'No matches found' text is untranslated
Description of problem: Search bar message is not translated.
Version-Release number of selected component (if applicable): 6.10.0
How reproducible: Always
Steps to Reproduce:
1. Login to Satellite 6.10 instance with any locale.
2. Navigate to [1] Infrastructure - Virt-who Configurations
3. Click on Create Config button
4. In any Search box drop down options try to search for wrong input, and look for non-marked strings.
Actual results: "No matches found" string is not translated.
Expected results: "No matches found" string should be marked as translatable string.
Additional info: Same thing has been observed in other pages as well with different locales, those are listed below.
[2] Hosts - Operating Systems -> click "Create Operating System" button, look for drop down and search wrong input into it.
[3] Hosts - Partition Tables -> click "Create Partition Table" button, look for drop down and search wrong input into it.
[4] Hosts - Installation Media -> click "Create Medium" button, look for drop down and search wrong input into it.
[5] Hosts - Provisioning Templates -> click "Create Template" button, switch to tab "Type" then look for drop down and search wrong input into it.
[6] Hosts - Job Templates -> click "New Job Template" button, switch to tab "Job" then look for drop down and search wrong input into it.
[7] Configure - Host Group -> click "Create Host Group" button, switch between tabs "Host Group", "Network" and "Operating System" then look for drop down and search wrong input into it.
[8] Configure - Discovery Rules -> click "Create Rule" button, look for drop down and search wrong input into it.
[9] Configure - Variables -> click "New Ansible Variable" button, look for drop down and search wrong input into it.
[10] Infrastructure - Subnets -> click "Create Subnet" button, switch between tabs "Subnet" and "Capsules" then look for drop down and search wrong input into it.
[11] Infrastructure - Domains -> click "Create Domain" button, look for drop down and search wrong input into it.
[12] Infrastructure - Compute Resources -> click "Create Compute Resource" button, look for drop down and search wrong input into it.
FailedQA:
Tested with:
- Satellite 6.12.0 snap 5
Test steps:
- Go to Infrastructure > Virt-who Configurations
- Click on Create Config button
- Click on any dropdown button and search for a non-existing entity.
Observations:
- Still see "No matches found" string, it's not translated.
Could you please re-check? If I turn on marking translated strings then it is marked as translated. It is possible that an actual translation for that string is missing, but that's not something we as developers can or should do.
satellite-6.12.0-2.el8sat.noarch
foreman-3.3.0.1-1.el8sat.noarch
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 (Important: Satellite 6.12 Release), 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-2022:8506
Created attachment 1825385 [details] [1] Infrastructure - Virt-who Configurations - 'No matches found' text is untranslated Description of problem: Search bar message is not translated. Version-Release number of selected component (if applicable): 6.10.0 How reproducible: Always Steps to Reproduce: 1. Login to Satellite 6.10 instance with any locale. 2. Navigate to [1] Infrastructure - Virt-who Configurations 3. Click on Create Config button 4. In any Search box drop down options try to search for wrong input, and look for non-marked strings. Actual results: "No matches found" string is not translated. Expected results: "No matches found" string should be marked as translatable string. Additional info: Same thing has been observed in other pages as well with different locales, those are listed below. [2] Hosts - Operating Systems -> click "Create Operating System" button, look for drop down and search wrong input into it. [3] Hosts - Partition Tables -> click "Create Partition Table" button, look for drop down and search wrong input into it. [4] Hosts - Installation Media -> click "Create Medium" button, look for drop down and search wrong input into it. [5] Hosts - Provisioning Templates -> click "Create Template" button, switch to tab "Type" then look for drop down and search wrong input into it. [6] Hosts - Job Templates -> click "New Job Template" button, switch to tab "Job" then look for drop down and search wrong input into it. [7] Configure - Host Group -> click "Create Host Group" button, switch between tabs "Host Group", "Network" and "Operating System" then look for drop down and search wrong input into it. [8] Configure - Discovery Rules -> click "Create Rule" button, look for drop down and search wrong input into it. [9] Configure - Variables -> click "New Ansible Variable" button, look for drop down and search wrong input into it. [10] Infrastructure - Subnets -> click "Create Subnet" button, switch between tabs "Subnet" and "Capsules" then look for drop down and search wrong input into it. [11] Infrastructure - Domains -> click "Create Domain" button, look for drop down and search wrong input into it. [12] Infrastructure - Compute Resources -> click "Create Compute Resource" button, look for drop down and search wrong input into it.