RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1677505 - The Japanese Era name will be changed on 2019-05-01 / component java-1.7.0-openjdk / rhel6
Summary: The Japanese Era name will be changed on 2019-05-01 / component java-1.7.0-op...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: java-1.7.0-openjdk
Version: 6.10
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Andrew John Hughes
QA Contact: OpenJDK QA
URL:
Whiteboard:
Depends On:
Blocks: 1688571
TreeView+ depends on / blocked
 
Reported: 2019-02-15 06:10 UTC by Christian Horn
Modified: 2021-08-30 13:13 UTC (History)
6 users (show)

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:
Clone Of: 1677504
: 1677510 1677511 1677512 1687324 (view as bug list)
Environment:
Last Closed: 2019-08-22 19:40:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2749651 0 Learn more None Does the change of the Japanese Era affect Red Hat Enterprise Linux? 2019-02-15 06:14:20 UTC

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.


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