Bug 1648601
Summary: | Upgrade to 6.4 migrate candlepin fails in java version 1.7.0 | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Paul Dudley <pdudley> |
Component: | Packaging | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED WONTFIX | QA Contact: | Lukas Pramuk <lpramuk> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.4 | CC: | bcourt, bkearney, egolov, ehelms, inecas, mbacovsk, pdudley, sadas |
Target Milestone: | Unspecified | Keywords: | Triaged, Upgrades |
Target Release: | Unused | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-21 17:07:28 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
Paul Dudley
2018-11-10 22:27:34 UTC
This issue is corrected via the following: - # alternatives --config java <select number for java-1.8.0> - # satellite-installer --upgrade 6.4 installs seem to always have 1.8.0 selected by default and this issue seems likely to only be hit by upgrade of Satellite whose Java version was never changed to 1.8.0. Currently, the issue was reproduced on Satellites that were upgraded from 6.1 to 6.4 and from 6.2 to 6.4. The upgrade should be installing the newer java as we do require Java 1.8 in Satellite 6.4. Paul can you confirm what version of the candlepin rpm file has been installed? I know Candlepin 2.4.9 which should be part of Satellite 6.4 requires java > 1.8. Also, if you could include the version of the java rpm installed on the system it would be helpful as well. The requires set here ensure that 1.8.0 is installed, and so far having 1.8.0 installed is not the problem. The problem only comes with the 1.8.0 version not being used when an upgrade occurs. [root@iridium ~]# rpm -q satellite foreman katello candlepin satellite-6.4.0-15.el7sat.noarch foreman-1.18.0.37-1.el7sat.noarch katello-3.7.0-8.el7sat.noarch candlepin-2.4.8-1.el7.noarch [root@iridium ~]# yum deplist katello-3.7.0-8.el7sat.noarch | grep java dependency: java-openjdk >= 1:1.7.0 provider: java-11-openjdk.x86_64 1:11.0.ea.28-7.el7 provider: java-11-openjdk.i686 1:11.0.ea.28-7.el7 provider: java-1.8.0-openjdk.x86_64 1:1.8.0.191.b12-1.el7_6 provider: java-1.8.0-openjdk.i686 1:1.8.0.191.b12-1.el7_6 provider: java-1.7.0-openjdk.x86_64 1:1.7.0.201-2.6.16.1.el7_6 dependency: java-openjdk < 1:1.8.0.45 provider: java-1.7.0-openjdk.x86_64 1:1.7.0.201-2.6.16.1.el7_6 [root@iridium ~]# yum deplist candlepin-2.4.8-1.el7.noarch | grep java dependency: java >= 1:1.8.0 provider: java-11-openjdk.x86_64 1:11.0.ea.28-7.el7 provider: java-11-openjdk.i686 1:11.0.ea.28-7.el7 provider: java-1.8.0-openjdk.x86_64 1:1.8.0.191.b12-1.el7_6 provider: java-1.8.0-openjdk.i686 1:1.8.0.191.b12-1.el7_6 It seems like availability of 1.8.0 isn't really a problem, just that we're not making sure java root 1.8.0 is set before the migration occurs? I am moving to packaging as the katello-3.7.0-8.el7sat.noarch should be depending on Java 1.8 or higher. However, this might be an installer issue in addition to a packaging issue. There is an upstream Patch that might be relevant. https://github.com/theforeman/foreman-packaging/commit/b9557f47bb05444f833e0e87c2f7c6f8978e3950 Barnaby, would it be possible for Candlepin to use /usr/lib/jvm/jre-1.8.0-openjdk/bin/java directly if it needs Java 1.8? /usr/bin/java can point to *anything* and we don't manage this alternative in our installer. Evgeni, Candlepin does not select the version of Java that is used, that is used by Tomcat or whatever the installer has set up prior to running liquibase. This is not something the Candlepin team can fix. 6.4 is now EOL, I am closing this out. |