Bug 2024750 - i18n some remaining OLM items
Summary: i18n some remaining OLM items
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.10
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.10.0
Assignee: Jakub Hadvig
QA Contact: Yanping Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-18 21:00 UTC by ralpert
Modified: 2022-03-10 16:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:29:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 10511 0 None open Bug 2024750: Fix OLM files in need of i18n 2021-11-18 21:03:55 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:30:04 UTC

Description ralpert 2021-11-18 21:00:50 UTC
Description of problem:
I found some files in the OLM package that hadn't been internationalized.

Version-Release number of selected component (if applicable):
4.10

How reproducible:
Always

Steps to Reproduce:
1. Look at file
2.
3.

Actual results:
Text is hard-coded

Expected results:
Text is internationalized

Additional info:

Comment 3 Yanping Zhang 2021-12-21 03:49:51 UTC
Checked on ocp 4.10 cluster with payload 4.10.0-0.nightly-2021-12-18-034942.
Checked on catalogsource creation page, edit registry pool page and so on, texts are marked for i18n.

Comment 8 errata-xmlrpc 2022-03-10 16:29:41 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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:0056


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