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 1679427 - Priority set for java-11-openjdk in alternatives --install is 1
Summary: Priority set for java-11-openjdk in alternatives --install is 1
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: java-11-openjdk
Version: 7.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: jiri vanek
QA Contact: OpenJDK QA
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-21 07:09 UTC by Divya
Modified: 2019-05-31 14:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-31 14:55:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Divya 2019-02-21 07:09:23 UTC
Description of problem:
java-11-openjdk is installed in the java family of alternatives system with priority 1 and hence does not become the default java for use after installation with other versions of openjdk preinstalled.

Version-Release number of selected component (if applicable):
java-11-openjdk

How reproducible:
Always

Steps to Reproduce:
1. Install java-11-openjdk using below command(some other openjdk should already be installed like java-1.8/7.0-openjdk): 

# yum install java-11-openjdk

2. Check the active version of java with below command: 

# java -version

3. Priority can be checked with below command: 

# alternatives --display java | grep priority


Actual results:
Upon installation java-11-openjdk does not become default java.

Expected results:
Upon installation, java-11-openjdk should become the default java.

Additional info:
Currently in java-11-openjdk.spec file, priority is specified as below: 

%global priority        00000%{minorver}1

IMHO it should be as below format: 

%global priority        1100%{minorver}%{buildver}  --> buildver should be 3 digit number

Comment 1 jiri vanek 2019-02-21 11:07:24 UTC
hi!

This is fully intentional, until openjd8 remains system jdk.

It can grow up a bit, (in case of IBM jdk11  goes in) but it will stay lower then jdk8 .

Not sure how jdk7 priority will affect jdk11 priority after jdk7 EOL.


Note You need to log in before you can comment on or make changes to this bug.