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 1659646 - Installing OpenJDK 11 breaks alternatives javac
Summary: Installing OpenJDK 11 breaks alternatives javac
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: java-11-openjdk
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: jiri vanek
QA Contact: OpenJDK QA
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-14 20:59 UTC by Mike Millson
Modified: 2018-12-17 10:18 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-12-17 10:18:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mike Millson 2018-12-14 20:59:16 UTC
Description of problem:
Installing OpenJDK11 broke javac alternative.

Version-Release number of selected component (if applicable):
java-11-openjdk-headless-11.0.1.13-3.el7_6.x86_64
java-11-openjdk-11.0.1.13-3.el7_6.x86_64
java-11-openjdk-devel-11.0.1.13-3.el7_6.x86_64


Steps to Reproduce:
1. yum install java-11*
2. alternatives --config javac

Actual results:
# alternatives --config javac
failed to read link /usr/bin/javac: No such file or directory

Expected results:
Should see the menu to select the javac version.

Additional info:
I can manually create the link (have to run command 2x):
# alternatives --install /usr/bin/javac javac /usr/lib/jvm/java-11-openjdk-11.0.1.13-3.el7_6.x86_64/bin/javac 180191
failed to read link /usr/bin/javac: No such file or directory
# alternatives --install /usr/bin/javac javac /usr/lib/jvm/java-11-openjdk-11.0.1.13-3.el7_6.x86_64/bin/javac 180191

Then can successfully run alternatives:

# alternatives --config javac

There are 4 programs which provide 'javac'.

  Selection    Command
-----------------------------------------------
 + 1           java-1.7.0-openjdk.x86_64 (/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.201-2.6.16.1.el7_6.x86_64/bin/javac)
   2           java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64/bin/javac)
*  3           /usr/java/jdk-11.0.1/bin/javac
   4           /usr/lib/jvm/java-11-openjdk-11.0.1.13-3.el7_6.x86_64/bin/javac

Enter to keep the current selection[+], or type selection number:

Comment 2 jiri vanek 2018-12-17 10:18:59 UTC
Acording to:

*  3           /usr/java/jdk-11.0.1/bin/javac

It is clear that you have installed oracle's RPMS. Oracle's ROMS are known tobe not compatible wiht anything reasonable on this planet.
You have deliberately crippled your system. There is no way how to help you.


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