Bug 2006974 - [ALL_LANG] [SAT_6.10 | 6.11] 'No matches found' text is untranslated in search bar
Summary: [ALL_LANG] [SAT_6.10 | 6.11] 'No matches found' text is untranslated in searc...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Search
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.12.0
Assignee: satellite6-bugs
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-22 18:37 UTC by visawant
Modified: 2022-11-16 13:33 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-16 13:32:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
[1] Infrastructure - Virt-who Configurations - 'No matches found' text is untranslated (124.44 KB, image/png)
2021-09-22 18:37 UTC, visawant
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 32476 0 Normal New 'No matches found' text is untranslated in search bar 2021-09-22 18:38:12 UTC
Red Hat Issue Tracker SAT-13529 0 None None None 2022-10-21 15:32:39 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:33:34 UTC

Description visawant 2021-09-22 18:37:14 UTC
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.

Comment 12 visawant 2022-05-05 10:23:24 UTC
This issue has been observed in 6.11.0 beta build.

Comment 13 Bryan Kearney 2022-06-06 12:04:09 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32476 has been resolved.

Comment 14 Jameer Pathan 2022-08-08 12:53:12 UTC
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.

Comment 15 Adam Ruzicka 2022-08-09 08:59:52 UTC
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

Comment 16 Jameer Pathan 2022-08-09 12:10:05 UTC
Thanks Adam. I tried what you suggested, and "No matches found" is marked as translated.

Comment 20 errata-xmlrpc 2022-11-16 13:32:46 UTC
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


Note You need to log in before you can comment on or make changes to this bug.