Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

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

https://access.redhat.com/errata/RHBA-2018:3017