Bug 1990024 - Eligible is misspelled in console-app
Summary: Eligible is misspelled in console-app
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.9.0
Assignee: ralpert
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-04 15:10 UTC by ralpert
Modified: 2021-10-18 17:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:44:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 9729 0 None None None 2021-08-04 15:26:00 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:44:53 UTC

Description ralpert 2021-08-04 15:10:58 UTC
Description of problem:
The word "eligible" is misspelled several times in the console-app plugin as "elligible." We should fix it.

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

How reproducible:
Always

Steps to Reproduce:
1. Search for "elligible" in the codebase

Actual results:
There are results.

Expected results:
There are no results.

Additional info:

Comment 2 Yadan Pei 2021-08-10 07:19:31 UTC
Search 'elligible' in console repo

$ grep -nr 'elligible' frontend/public/
frontend/public//locales/ja/public.json:1694:  "If no pod selector is provided, traffic from all pods in elligible namespaces will be allowed.": "Pod セレクターが指定されていない場合、対象となる namespace のすべての Pod からのトラフィックが許可されます。",
frontend/public//locales/ja/public.json:1696:  "If no pod selector is provided, traffic to all pods in elligible namespaces will be allowed.": "Pod セレクターが指定されていない場合、対象となる namespace のすべての Pod へのトラフィックが許可されます。",
frontend/public//locales/ja/public.json:1698:  "If no namespace selector is provided, pods from all namespaces will be elligible.": "namespace セレクターが指定されていない場合、すべての namespace からの Pod が対象となります。",
frontend/public//locales/zh/public.json:1694:  "If no pod selector is provided, traffic from all pods in elligible namespaces will be allowed.": "如果没有提供 pod 选择器,则允许来自有效命名空间中的所有 pod 的流量。",
frontend/public//locales/zh/public.json:1696:  "If no pod selector is provided, traffic to all pods in elligible namespaces will be allowed.": "如果没有提供 pod 选择器,则允许到有效命名空间中的所有 pod 的流量。",
frontend/public//locales/zh/public.json:1698:  "If no namespace selector is provided, pods from all namespaces will be elligible.": "如果没有提供命名空间选择器,则来自所有命名空间中的 pod 都将是有效的。",
frontend/public//locales/ko/public.json:1694:  "If no pod selector is provided, traffic from all pods in elligible namespaces will be allowed.": "pod 선택기가 제공되지 않으면 적합한 네임스페이스에 있는 모든 pod의 트래픽이 허용됩니다.",
frontend/public//locales/ko/public.json:1696:  "If no pod selector is provided, traffic to all pods in elligible namespaces will be allowed.": "pod 선택기가 제공되지 않으면 적합한 네임스페이스의 모든 pod에 대한 트래픽이 허용됩니다.",
frontend/public//locales/ko/public.json:1698:  "If no namespace selector is provided, pods from all namespaces will be elligible.": "네임스페이스 선택기가 제공되지 않으면 모든 네임스페이스의 pod를 사용할 수 있습니다.",

The word still appear in public.json for ja & zh & ko, shall we remove them? 

Assign back for confirmation

Comment 3 ralpert 2021-08-10 13:05:46 UTC
These will be removed by the QE team in the next handoff. Any changes we make locally just get overwritten so it's not really worth it.

Comment 4 Yadan Pei 2021-08-16 12:59:34 UTC
Moving the bug to VERIFIED based on comment 2 and comment 3 since everything is working as expected

Comment 5 ralpert 2021-08-16 13:27:02 UTC
Thanks Yadan. :) 

Just in case this is ever seen by a human again: I meant the translation team rather than QE in comment #3.

Comment 8 errata-xmlrpc 2021-10-18 17:44:52 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.9.0 bug fix and 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-2021:3759


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