Bug 1631249 - Make sure RHV Manager will use OpenJDK 8 even when newer versions are available
Summary: Make sure RHV Manager will use OpenJDK 8 even when newer versions are available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.2.7
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ovirt-4.3.0
: 4.3.0
Assignee: Martin Perina
QA Contact: Pavol Brilla
URL:
Whiteboard:
Depends On:
Blocks: 1632244
TreeView+ depends on / blocked
 
Reported: 2018-09-20 10:03 UTC by Petr Balogh
Modified: 2019-05-08 12:38 UTC (History)
8 users (show)

Fixed In Version: ovirt-engine-4.3.0_alpha
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1632244 (view as bug list)
Environment:
Last Closed: 2019-05-08 12:38:22 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:1085 0 None None None 2019-05-08 12:38:39 UTC
oVirt gerrit 94443 0 'None' MERGED core: Require specifically OpenJDK 8 2020-10-30 09:16:46 UTC
oVirt gerrit 94447 0 'None' MERGED core: Require specifically OpenJDK 8 2020-10-30 09:16:46 UTC

Description Petr Balogh 2018-09-20 10:03:03 UTC
Description of problem:

There is problem that we got newer version of Java from 7.6 base repo than is required by engine.


Version-Release number of selected component (if applicable):
rhv-4.2.7-2

How reproducible:
Install rhel 7.6 add RHV release RPM and run engine-setup.


Actual results:
Failing with 
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod
    method['method']()
  File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/ovirt-engine-common/config/java.py", line 69, in _validation
    ] = java.Java().getJavaHome()
  File "/usr/lib/python2.7/site-packages/ovirt_engine/java.py", line 59, in getJavaHome
    error='(%s)' % stderr if stderr else '',
RuntimeError: Cannot get JAVA_HOME make sure supported JRE is installed
2018-09-19 21:26:22,902+0300 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Setup validation': Cannot get JAVA_HOME make sure supported JRE is installed

Expected results:
Pass the engine-setup

Additional info:
Installed JDK:
rpm -qa | grep jdk                                                                           
eap7-jackson-datatype-jdk8-2.8.11-1.redhat_1.1.ep7.el7.noarch
eap7-jboss-openjdk-orb-8.0.8-2.Final_redhat_1.1.ep7.el7.noarch
java-11-openjdk-headless-11.0.ea.28-4.el7.x86_64
copy-jdk-configs-3.3-10.el7_5.noarch
java-11-openjdk-11.0.ea.28-4.el7.x86_64

 yum info java-11-openjdk-headless-11.0.ea.28-4.el7.x86_64
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager, versionlock                      
This system is not registered with an entitlement server. You can use subscription-manager to register.              
Installed Packages                                                                                                   
Name        : java-11-openjdk-headless                                                                               
Arch        : x86_64
Epoch       : 1
Version     : 11.0.ea.28
Release     : 4.el7
Size        : 160 M
Repo        : installed
From repo   : rhel-7.6-base
Summary     : OpenJDK Headless Runtime Environment 11
URL         : http://openjdk.java.net/
License     : ASL 1.1 and ASL 2.0 and BSD and BSD with advertising and GPL+ and GPLv2 and GPLv2 with exceptions and IJG and LGPLv2+ and MIT and MPLv2.0 and Public Domain and
            : W3C and zlib and ISC and FTL and RSA
Description : The OpenJDK runtime environment 11 without audio and video support.

Comment 2 Martin Perina 2018-09-20 10:07:35 UTC
OpenJDK 11 is introduced in RHEL 7.6, but we cannot use it and we need to stay on OpenJDK 8

Comment 3 Marina Kalinin 2018-09-20 14:32:13 UTC
Petr,
Can you please confirm that it will not impact existing installations. And even if running yum upgrade on the manager would not bring OpenJDK 11.

Comment 4 Martin Perina 2018-09-20 19:23:54 UTC
(In reply to Marina from comment #3)
> Petr,
> Can you please confirm that it will not impact existing installations. And
> even if running yum upgrade on the manager would not bring OpenJDK 11.

Upgrades from previous version shouldn't be affected, because on those machines we already have install java-1.8.0-openjdk-headless which provides 'java-openjdk-headles >= 1.8.0' which we require. But for new installations on RHEL 7.6 java-11-openjdk-headless will be installed, because yum will always select highest available version. Because of that we need to change our requirements from 'java-openjdk-headles >= 1.8.0' to 'java-1.8.0-openjdk-headles >= 1.8.0' so java-11 will not be installed.

Comment 5 Petr Balogh 2018-09-21 07:47:49 UTC
When in our playbook we installed java-1.8.0-openjdk-headles and after all our flow I see that we have now these jdk packages installed on the system
rpm -qa |grep jdk
java-1.8.0-openjdk-headless-1.8.0.181-7.b13.el7.x86_64
eap7-jboss-openjdk-orb-8.0.8-2.Final_redhat_1.1.ep7.el7.noarch
java-11-openjdk-headless-11.0.ea.28-6.el7.x86_64
eap7-jackson-datatype-jdk8-2.8.11-1.redhat_1.1.ep7.el7.noarch
java-11-openjdk-11.0.ea.28-6.el7.x86_64
copy-jdk-configs-3.3-10.el7_5.noarch

Comment 6 RHV bug bot 2018-09-21 11:46:06 UTC
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]

For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]

For more info please contact: rhv-devops

Comment 8 Pavol Brilla 2018-10-09 09:25:48 UTC
Verified

]#  yum deplist ovirt-engine | grep openjdk ; yum list ovirt-engine
  dependency: java-1.8.0-openjdk-headless >= 1:1.8.0
   provider: java-1.8.0-openjdk-headless.x86_64 1:1.8.0.181-7.b13.el7
   provider: java-1.8.0-openjdk-headless.i686 1:1.8.0.181-7.b13.el7
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager, versionlock
This system is not registered with an entitlement server. You can use subscription-manager to register.
Installed Packages
ovirt-engine.noarch                                   4.3.0-0.0.master.20181008123033.gitf23e91f.el7                                   @ovirt-master-snapshot

[root@system-ge-4 ~]# yum list \*jdk\*
Installed Packages
copy-jdk-configs.noarch                                                      3.3-10.el7_5                                              @rhel-7.6-base        
java-1.8.0-openjdk-headless.x86_64                                           1:1.8.0.181-7.b13.el7                                     @rhel-7.6-base        
java-11-openjdk.x86_64                                                       1:11.0.ea.28-7.el7                                        @rhel-7.6-base        
java-11-openjdk-headless.x86_64                                              1:11.0.ea.28-7.el7                                        @rhel-7.6-base        
Available Packages

Comment 9 Randy Martinez 2018-11-06 16:35:26 UTC
Until the issue is resolved, a temp workaround I've used is:

1. install prereqs & run engine-setup(expecting configuration failure).
2. rpm -e --nodeps java-11-openjdk.x86_64 java-11-openjdk-headless.x86_64
3. yum install java-1.8.0-openjdk.x86_64 java-1.8.0-openjdk-headless.x86_64
4. disable rhel-7-server-rpms repo
5. proceed with install.

Comment 10 Martin Perina 2018-11-06 16:54:49 UTC
(In reply to Randy Martinez from comment #9)
> Until the issue is resolved, a temp workaround I've used is:
> 
> 1. install prereqs & run engine-setup(expecting configuration failure).
> 2. rpm -e --nodeps java-11-openjdk.x86_64 java-11-openjdk-headless.x86_64
> 3. yum install java-1.8.0-openjdk.x86_64 java-1.8.0-openjdk-headless.x86_64
> 4. disable rhel-7-server-rpms repo
> 5. proceed with install.

This issue is already resolved in RHV 4.2.7, see the cloned bug BZ1632244

Comment 11 Raz Tamir 2018-11-26 16:31:38 UTC
QE verification bot: the bug was verified upstream

Comment 13 errata-xmlrpc 2019-05-08 12:38:22 UTC
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://access.redhat.com/errata/RHEA-2019:1085


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