This is the successor to bug 1307108, bug 1335322, bug 1359857, bug 1391132, bug 1508017 and bug 1538772.
With RHEL 7, we aim to provide the "latest and greatest" version of OpenJDK to end users as soon as possible (see bug 922089).
Oracle began maintenance of OpenJDK 8 by making two releases in tandem at quarterly points through the year (January, April, July & October). One was a security update that we shipped immediately via async errata, and backport to OpenJDK 6 & 7 as well. There was also a bug fix update which includes both security fixes and other bug fixes. It is this release which then forms the basis for the security update three months later.
Despite stalling between October 2016 and October 2017, this process now seems to be back on track. In April 2018, 8u171 (which we shipped to customers on all RHEL platforms) and 8u172 were released. This means that the July 2018 security update, 8u181, will be based on 8u172.
As such, it would be good to get u172 into RHEL ahead of this security update to reduce the potential for problems.
To actually fulfil our promise of the "latest and greatest", this should go out to users via z-stream in RHEL 7.5, as we have in the past.
Requesting z-stream so we can meet the "latest and greatest" aim.
surpassed by JDK 8u181 (java-1.8.0-openjdk-22.214.171.124-4.b04.el7)
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.