Bug 1677092

Summary: The Japanese Era name will be changed on 2019-05-01 / component icu / rhel7
Product: Red Hat Enterprise Linux 7 Reporter: Christian Horn <chorn>
Component: icuAssignee: Mike FABIAN <mfabian>
Status: CLOSED ERRATA QA Contact: QE Internationalization Bugs <qe-i18n-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.0CC: ahogbin, bbarve, desktop-qa-list, mfabian, petersen, rdave, smaitra, tpelka
Target Milestone: rcKeywords: Rebase
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1677090
: 1677093 (view as bug list) Environment:
Last Closed: 2019-08-06 13:18:17 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: 1677090    
Bug Blocks: 1640542, 1677091, 1677093, 1688570, 1707454    

Description Christian Horn 2019-02-14 02:49:06 UTC
+++ This bug was initially created as a clone of Bug #1677090 +++

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

(snippet from the rhel7 icu code)
 364 void IntlCalendarTest::TestJapanese() {
 365     UDate timeA = Calendar::getNow();
 366     
 367     /* Sorry.. japancal.h is private! */
 368 #define JapaneseCalendar_MEIJI  232
 369 #define JapaneseCalendar_TAISHO 233
 370 #define JapaneseCalendar_SHOWA  234
 371 #define JapaneseCalendar_HEISEI 235
 372     
 373     // BE 2542 == 1999 CE
 374     int32_t data[] = { 
 375         //       Jera         Jyr  Gyear   m             d
 376         JapaneseCalendar_MEIJI, 1, 1868, UCAL_SEPTEMBER, 8,
 377         JapaneseCalendar_MEIJI, 1, 1868, UCAL_SEPTEMBER, 9,
 378         JapaneseCalendar_MEIJI, 2, 1869, UCAL_JUNE, 4,
 379         JapaneseCalendar_MEIJI, 45, 1912, UCAL_JULY, 29,
 380         JapaneseCalendar_TAISHO, 1, 1912, UCAL_JULY, 30,
 381         JapaneseCalendar_TAISHO, 1, 1912, UCAL_AUGUST, 1,
 382         
 383         // new tests (not in java)
 384         JapaneseCalendar_SHOWA,     64,   1989,  UCAL_JANUARY, 7,  // Test current era transition (different code path than others)
 385         JapaneseCalendar_HEISEI,    1,   1989,  UCAL_JANUARY, 8,
 386         JapaneseCalendar_HEISEI,    1,   1989,  UCAL_JANUARY, 9,
 387         JapaneseCalendar_HEISEI,    1,   1989,  UCAL_DECEMBER, 20,
 388         JapaneseCalendar_HEISEI,  15,  2003,  UCAL_MAY, 22,
 389         -1,-1,-1,-1,-1,-1,-1,-1,-1,-1
 390     };

Actual results:
No reference to the upcoming era.

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 openjdk.

Comment 5 Satyabrata Maitra 2019-05-27 10:18:37 UTC
Sure, we will test this.

Comment 6 Jens Petersen 2019-06-20 14:50:44 UTC
Not sure why this bug didn't move to VERIFIED.
Though the errata says "State REL_PREP invalid."?

Any idea, Tomas?

Comment 7 Jens Petersen 2019-06-20 15:17:37 UTC
Okay I guess the errata is fine: that invalid state just refers to pushing to CDN.

Seems VERIFIED can only be set by ET?

Comment 8 Tomas Pelka 2019-06-21 09:48:54 UTC
(In reply to Jens Petersen from comment #7)
> Okay I guess the errata is fine: that invalid state just refers to pushing
> to CDN.
> 
> Seems VERIFIED can only be set by ET?

Well that is actually not true, QE should set to verified before erratum is moved to REL_PREP. Because REL_PREP means QE is done with it, including bug verification.

Satya maybe somebody just forgot about this bz?

Comment 9 Satyabrata Maitra 2019-06-24 04:32:53 UTC
QE will finish verification of this bug by EOD. We are already in process.

Comment 12 errata-xmlrpc 2019-08-06 13:18:17 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:2328