Bug 1072295

Summary:	[Openjdk update] alternative was not updated after Openjdk update
Product:	[Fedora] Fedora	Reporter:	Frederic Hornain <fhornain>
Component:	java-1.7.0-openjdk	Assignee:	jiri vanek <jvanek>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	20	CC:	ahughes, dbhole, jerboaa, jvanek, madko, omajid, rlledo
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-05 09:47: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 Frederic Hornain 2014-03-04 10:26:01 UTC

Description of problem:

Well,I can not explain the root cause.
I did an update of OpenJDK - java-1.7.0-openjdk-1.7.0.60-2.4.5.1.fc20.x86_64 - on my F20.
Then I was not able to lauch the "java" or "javac" command from the prompt.

[fhornain@localhost ~]$ java
bash: java: command not found...

I am assuming the "aternatives" program was not updated in consequence after the 
java-1.7.0-openjdk-1.7.0.60-2.4.4.0.fc20.x86_64 update.
 
At the end, java and javac binary are there but the link is wrong.

WORKAROUND
I had to update the link in the alternative program myself.

Comment 1 jiri vanek 2014-03-05 09:47:27 UTC

Hi.

In f19 and older, the alternatives were always forcibly set. In f20, if you are in manual mode (and so you are) alternatives are not set.

The forcible set in f19 and older was and workaround to fix one feature (multiple jdks) and one bug (typo in alternative key). But we can not set alternatives forcibly if they are in manual mode - it is mostly in purpose[1].

If your alternatives are in manual mode, and you are not aware, then you could be facing the bug from past - recent selinux bug[0] or jdk older alternatives bug[2].

The best fix (to prevent future manual work) is to clean up alternatives manualy[0].

Especially[0] is god to read, as there s explanation of selinux bug and way how to force alternatives to set up (temporarily) snd last few comments give you an look into how to clean up alternatives.

Sorry for troubles.

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1056187 and https://bugzilla.redhat.com/show_bug.cgi?id=1049015
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1054321
[2] https://bugzilla.redhat.com/show_bug.cgi?id=991762 and https://bugzilla.redhat.com/show_bug.cgi?id=1056264 and https://bugzilla.redhat.com/show_bug.cgi?id=1013379

*** This bug has been marked as a duplicate of bug 1056187 ***

Comment 2 jiri vanek 2014-03-10 11:50:10 UTC

*** Bug 1074191 has been marked as a duplicate of this bug. ***

Comment 3 jiri vanek 2014-03-12 09:52:25 UTC

*** Bug 1074191 has been marked as a duplicate of this bug. ***

Comment 4 jiri vanek 2014-03-13 07:18:58 UTC

*** Bug 1075188 has been marked as a duplicate of this bug. ***