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.

Bug 1797054

Summary: java-11-openjdk-headless RPM does not provide java-headless capability
Product: Red Hat Enterprise Linux 8 Reporter: Hynek Mlnarik <hmlnarik>
Component: java-11-openjdkAssignee: jiri vanek <jvanek>
Status: CLOSED NOTABUG QA Contact: OpenJDK QA <java-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.4   
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-03 10:37:04 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 Hynek Mlnarik 2020-01-31 19:53:54 UTC
Description of problem:
RPM package java-11-openjdk-headless version does not provide java-headless which means installing a huge extraneous package into e.g. an OpenShift image, increasing its size by ~ 100 MiB

Version-Release number of selected component (if applicable):
11.0.6.10

How reproducible:
Always

Steps to Reproduce:
1. Install java-11-openjdk-headless
2. Install mariadb-java-client, maven-lib, postgresql-jdbc or other package depending on java-headless >= ...

Actual results:
java-1.8.0-openjdk-headless is installed along the way

Expected results:
java-1.8.0-openjdk-headless is NOT installed along the way, and JDK 11 is used

Additional info:
There is no "Provides" capability for java-headless in the package:

# rpm -q --provides java-11-openjdk-headless
config(java-11-openjdk-headless) = 1:11.0.6.10-0.el8_1
java-11-headless = 1:11.0.6.10-0.el8_1
java-11-openjdk-headless = 1:11.0.6.10-0.el8_1
java-11-openjdk-headless(x86-64) = 1:11.0.6.10-0.el8_1
jre-11-headless = 1:11.0.6.10-0.el8_1
jre-11-openjdk-headless = 1:11.0.6.10-0.el8_1

Since I cannot enter ref to SSO jira into links, pasting it here: https://issues.redhat.com/browse/KEYCLOAK-12868

Comment 1 jiri vanek 2020-02-03 10:37:04 UTC
Hi. This is intentional. It will be added once jdk8 will stop to be the system JDK.

If you need this, install mariadb, then insntall jre11-headless and then rpm -e --nodeps jdk8.   

The reason is, that no one currently guarantee that java stack will work with jdk11. We are slowly moving to make jdk11 default in fedora, once this pass, we can move to rhel. Sorry for bad news.

Comment 2 Hynek Mlnarik 2020-02-04 14:16:48 UTC
Thanks for the explanation, understood. We will use the suggested workaround for the time being then.