Bug 2052674 - Remove extra spaces
Summary: Remove extra spaces
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Yadan Pei
QA Contact: Yadan Pei
Depends On:
TreeView+ depends on / blocked
Reported: 2022-02-09 18:43 UTC by ralpert
Modified: 2022-08-10 10:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-08-10 10:48:34 UTC
Target Upstream Version:

Attachments (Terms of Use)
extra space has been removed (108.67 KB, image/png)
2022-02-11 10:03 UTC, Yadan Pei
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 11021 0 None open Fix Bug 2052674: Remove a couple of extra spaces 2022-02-09 18:50:20 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:49:02 UTC

Description ralpert 2022-02-09 18:43:30 UTC
Description of problem:
There are extra spaces in a couple of strings in frontend/public/locales/ja/public.json:
* "The debug pod failed. "
* "API failed to return the Service Level Agreement setting for this cluster.  Check again later."

We should fix them.

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

How reproducible:

Steps to Reproduce:
1. Look at text in frontend/public/locales/ja/public.json

Actual results:
Extra spaces

Expected results:
No extra spaces

Additional info:

Comment 3 Yadan Pei 2022-02-11 10:03:45 UTC
Created attachment 1860564 [details]
extra space has been removed

extra space has been removed

verified on 4.11.0-0.nightly-2022-02-10-180317

Comment 5 errata-xmlrpc 2022-08-10 10:48:34 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: OpenShift Container Platform 4.11.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.


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