Bug 1677505

Summary: The Japanese Era name will be changed on 2019-05-01 / component java-1.7.0-openjdk / rhel6
Product: Red Hat Enterprise Linux 6 Reporter: Christian Horn <chorn>
Component: java-1.7.0-openjdkAssignee: Andrew John Hughes <ahughes>
Status: CLOSED CURRENTRELEASE QA Contact: OpenJDK QA <java-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.10CC: ahogbin, ahughes, dbhole, java-qa, jdoyle, jvanek
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: java-1.7.0-openjdk-1.7.0.221-2.6.18.0.el6_10 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1677504
: 1677510 1677511 1677512 1687324 (view as bug list) Environment:
Last Closed: 2019-08-22 19:40:25 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: 1688571    

Description Christian Horn 2019-02-15 06:10:23 UTC
+++ This bug was initially created as a clone of Bug #1677504 +++

+++ This bug was initially created as a clone of Bug #1677502 +++

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.

--- Additional comment from RHEL Product and Program Management on 2019-02-15 06:08:46 UTC ---

Since this bug report was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.

Comment 2 jiri vanek 2019-03-12 15:00:39 UTC
Hi! This will go with next cpu, right?

Comment 3 jiri vanek 2019-03-13 11:09:20 UTC
Clarified, will be included in next CPU, this acking, as there is reserved workload for this time.

Comment 7 Andrew John Hughes 2019-08-22 19:40:25 UTC
This was fixed in the April 2019 update across all versions of RHEL: http://bitly.com/it20618

Comment 8 Christian Horn 2019-08-23 00:39:10 UTC
Seems like java-1.7.0-openjdk-1.7.0.221-2.6.18.0.el6_10
from https://access.redhat.com/errata/RHSA-2019:0790 is the
errata which first included the fix.