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 similar to previous bugs like 1649852, but reflects the new release process where Red Hat are also maintaining OpenJDK 11u upstream.

We have regular security updates of the OpenJDK packages every three months. At present, updates from one upstream version to another all end up going in during a short two week period before the release, because that's when we have the full set of security patches, and hence security bugs under which to commit them.

It would be preferable to avoid this bottleneck by updating to early builds of the next OpenJDK release in y-stream, so that the actual updates required for the security release is just the actual security patches.

Building in RHEL early enables us to avoid potential issues that are limited to certain architectures we support, but that aren't commonly used by developers (e.g. ppc64, ppc64le, s390 & s390x). This is why I've chosen RHEL 7 for this bug, as it has the full complement of architectures we need to build on.

Flipping to RHEL 7.8, but this will obviously be resolved by the updates next month.

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-2020:1088