Bug 1705329

Summary:	Update OpenJDK to 11.0.4 ahead of the July 2019 security update
Product:	Red Hat Enterprise Linux 7	Reporter:	Andrew John Hughes <ahughes>
Component:	java-11-openjdk	Assignee:	Andrew John Hughes <ahughes>
Status:	CLOSED ERRATA	QA Contact:	OpenJDK QA <java-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.6	CC:	dbhole, jomurphy, jvanek, zzambers
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	java-11-openjdk-11.0.4.11-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-31 19:57:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andrew John Hughes 2019-05-02 03:34:06 UTC

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.

Comment 3 Andrew John Hughes 2019-06-28 17:06:53 UTC

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

Comment 7 errata-xmlrpc 2020-03-31 19:57:27 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-2020:1088