Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1930444

Summary:	Lost ability to localize timestamps for en-gb locale
Product:	OpenShift Container Platform	Reporter:	ralpert
Component:	Management Console	Assignee:	Samuel Padgett <spadgett>
Status:	CLOSED DUPLICATE	QA Contact:	Yadan Pei <yapei>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.7	CC:	aos-bugs, jokerman, spadgett
Target Milestone:	---	Keywords:	i18n
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Scrubbed
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-04-16 15:28:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description ralpert 2021-02-18 22:00:26 UTC

Description of problem:
We regressed and lost the ability to localize timestamps for en-gb.

I think it's related to https://github.com/openshift/console/pull/8100. We should explore other options that will allow us to maintain sub-language functionality while minimizing the number of network requests.

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

How reproducible:
Always.

Steps to Reproduce:
1. Add ?lng=en-gb to the console URL.

Actual results:
Timestamps remain in en format rather than being in en-gb format.

Expected results:
Timestamps are in en-gb format.

Comment 1 Samuel Padgett 2021-03-22 13:48:37 UTC

We should look at taking a similar approach as in https://github.com/openshift/console/pull/8365 to localizing times. We have https://issues.redhat.com/browse/CONSOLE-2790 open to move away from moment.js.

Comment 2 Samuel Padgett 2021-04-01 14:45:03 UTC

This will be fixed by https://github.com/openshift/console/pull/8490.

Comment 3 Samuel Padgett 2021-04-16 15:28:44 UTC

This was fixed as part of bug 1862084.

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