Bug 1677516

Summary: The Japanese Era name will be changed on 2019-05-01 / component java-11-openjdk / rhel7
Product: Red Hat Enterprise Linux 7 Reporter: Christian Horn <chorn>
Component: java-11-openjdkAssignee: Andrew John Hughes <ahughes>
Status: CLOSED ERRATA QA Contact: OpenJDK QA <java-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.0CC: ahughes, amike, dbhole, java-qa, jvanek, jwright, zzambers
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: java-11-openjdk- Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1677512 Environment:
Last Closed: 2019-08-06 12:42:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: Red Hat1644888, 1688571, Red Hat1707454    

Description Christian Horn 2019-02-15 06:46:37 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.
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 jiri vanek 2019-03-07 07:25:04 UTC
should be covered by tck in limited scope

Comment 4 Christian Horn 2019-04-23 00:05:05 UTC
Seems to be resolved in https://access.redhat.com/errata/RHSA-2019:0778 .
Should we close this CURRENTRELEASE?

Comment 5 Joe Wright 2019-04-25 12:14:44 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 8 errata-xmlrpc 2019-08-06 12:42:57 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.