Bug 1251560
| Summary: | openjdk 1.8.0 alternative is changed to 1.7.0 when a 1.8.0 update is applied. | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Chris Williams <cww> | |
| Component: | java-1.8.0-openjdk | Assignee: | jiri vanek <jvanek> | |
| Status: | CLOSED ERRATA | QA Contact: | Lukáš Zachar <lzachar> | |
| Severity: | high | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 6.8 | CC: | btotty, dbhole, dkochuka, esammons, jbnance, jvanek, lzachar, salmy | |
| Target Milestone: | rc | Keywords: | Reopened, ZStream | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1254198 1336545 (view as bug list) | Environment: | ||
| Last Closed: | 2016-05-10 21:04:14 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1172231, 1254198, 1271375, 1336545 | |||
|
Description
Chris Williams
2015-08-07 17:27:16 UTC
*** Bug 1173503 has been marked as a duplicate of this bug. *** Fixed like this: http://pkgs.devel.redhat.com/cgit/rpms/java-1.8.0-openjdk/commit/?id=e2709783d7d892acc9df019de97386e4d06a8be3 and built: https://brewweb.devel.redhat.com/buildinfo?buildID=452472 I DON'T recommend this as bugfix for 6.7 Z stream, because: - https://bugzilla.redhat.com/show_bug.cgi?id=1217177#c49 is fixing the symptomps - change in priority handling is much bigger change then it looks. For record, part of this bugfix was http://pkgs.devel.redhat.com/cgit/rpms/java-1.8.0-openjdk/commit/?h=rhel-6.8&id=e2709783d7d892acc9df019de97386e4d06a8be3 That means taht priority of openjdk8 is now highest of all jdks in rhel 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://rhn.redhat.com/errata/RHEA-2016-0816.html |