Bug 1982675 - Workloads - DepolymentConfigs - Edit DeploymentConfig : i18n misses
Summary: Workloads - DepolymentConfigs - Edit DeploymentConfig : i18n misses
Keywords:
Status: CLOSED DUPLICATE of bug 1986495
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.9
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
: 4.9.0
Assignee: Bryan Florkiewicz
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-15 12:04 UTC by Krishna Babu K
Modified: 2021-08-11 22:16 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-11 22:14:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
'Strategy type' menu items and their description are not i18nized (211.18 KB, image/png)
2021-07-15 12:04 UTC, Krishna Babu K
no flags Details

Description Krishna Babu K 2021-07-15 12:04:27 UTC
Created attachment 1801850 [details]
'Strategy type' menu items and their description are not i18nized

Description of problem:
On navigation of Workloads - DepolymentConfigs - Edit DeploymentConfig, 
'Strategy type' menu items and their descriptions are not pseudolocalized.

1. Rolling: The rolling strategy will wait for pods to pass their readiness check, scale down old components and then scale up.
2. Recreate: The recreate strategy has basic rollout behavior and supports lifecycle hooks for injecting code into the deployment process.
3. Custom: The custom strategy allows you to specify container image that will provide your own deployment behavior.

Version-Release number of selected component (if applicable):
4.9.0-0.nightly-2021-07-14-083200

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
content is not i18nized 

Expected results:
content should be i18nized

Additional info:

Comment 1 Bryan Florkiewicz 2021-08-11 22:14:04 UTC

*** This bug has been marked as a duplicate of bug 1986495 ***


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