Bug 1677511

Summary:	The Japanese Era name will be changed on 2019-05-01 / component java-1.8.0-openjdk / rhel7
Product:	Red Hat Enterprise Linux 7	Reporter:	Christian Horn <chorn>
Component:	java-1.8.0-openjdk	Assignee:	Andrew John Hughes <ahughes>
Status:	CLOSED ERRATA	QA Contact:	OpenJDK QA <java-qa>
Severity:	medium	Docs Contact:
Priority:	urgent
Version:	7.7	CC:	ahogbin, ahughes, amike, chorn, dbhole, fkrska, fred.kubli, hmatsumo, java-qa, jvanek, jwright, mmiura, tnagata, zzambers
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	java-1.8.0-openjdk-1.8.0.212.b03-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1677505
Clones:	1705367 1705368 (view as bug list)		Environment:
Last Closed:	2019-08-06 12:33:48 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1644888, 1688571, 1705367, 1705368, 1707454

Description Christian Horn 2019-02-15 06:41:06 UTC

Description of problem:
The Japanese Era name will be changed on 2019-05-01 / component icu / rhel5
openjdk code is referring to the japanese era name.

All openjdk versions are affected.

Expected results:
The upcoming era name should properly be dealed with.

Additional info:
- https://en.wikipedia.org/wiki/Japanese_imperial_transition,_2019
- the new era name has not yet been announced.
- We also have to modify glibc (for example bz1555189) and icu.
- openjdk upstream seems to have implemented the new era now, with name NEWERA, which they
intend to replace then later.  I guess they wanted to be sure to have time to debug
issues they might have with the change itself now that there is time, and later just
want to replace the era.
http://hg.openjdk.java.net/jdk/jdk/rev/2e3f73b616c2
https://bugs.openjdk.java.net/browse/JDK-8202088
https://bugs.openjdk.java.net/browse/JDK-8205432
We are not necessarily requesting this in-between-step, the request of our customers is to have openjdk eventually deal with the new era name.

Comment 1 Andrew John Hughes 2019-03-01 19:33:21 UTC

We seem to be missing one of these bugs for the java-1.7.0-openjdk & RHEL 7 combination.

Comment 2 Christian Horn 2019-03-07 06:24:10 UTC

(In reply to Andrew John Hughes from comment #1)
> We seem to be missing one of these bugs for the java-1.7.0-openjdk & RHEL 7
> combination.

Sorry, I do not understand this, can you be more verbose?
Are there additional issues to be solved to solve this one here?  If so, are these reported as bz's already or not?

Comment 3 jiri vanek 2019-03-07 07:32:10 UTC

partially covered by tck

Comment 6 Christian Horn 2019-03-11 09:20:57 UTC

bz1687324 - The Japanese Era name will be changed on 2019-05-01 / component java-1.7.0-openjdk / rhel7

Comment 7 Andrew John Hughes 2019-03-12 04:21:00 UTC

Yes, that's what I meant, sorry for the confusion and thanks Christian for creating the missing bug.

Comment 11 Christian Horn 2019-04-23 00:03:04 UTC

Resolved in https://access.redhat.com/errata/RHSA-2019:0775 .  Should we close this bz CURRENTRELEASE?

Comment 12 Joe Wright 2019-04-25 12:15:16 UTC

Can we get the release notes updated for this ERRATA if the patch for this was included? The release notes do not include anything regarding updates for the Era change.

Comment 19 errata-xmlrpc 2019-08-06 12:33:48 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, 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/RHBA-2019:2006