Bug 2127210

Summary:	Older java 1.8 is still being needed on RHEL 8
Product:	Red Hat Enterprise Linux 8	Reporter:	Sahil Bhasin <sabhasin>
Component:	tomcatjss	Assignee:	RHCS Maintainers <rhcs-maint>
Status:	CLOSED MIGRATED	QA Contact:	idm-cs-qe-bugs
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	ckelley, peter.vreman
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-19 13:15:29 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 Sahil Bhasin 2022-09-15 17:19:05 UTC

Description of problem:
When Checking the RHEL 8, we see two Java 1.8 and Java 11 are installed, By looking at the requirements we saw that both are dependencies of Candlepin. 

Why older java 1.8 is still being needed on RHEL 8? Multiple java versions are not good from the security point of view.

[root@satellite ~]# rpm -q --requires tomcatjss
apache-commons-lang3
java-1.8.0-openjdk-headless
jpackage-utils >= 0:1.7.5-15
jss >= 4.9.0
jss < 5.0.0
pki-servlet-engine >= 1:9.0.7
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
slf4j
slf4j-jdk14

[root@satellite ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.6 (Ootpa)

[root@satellite ~]# rpm -q --requires candlepin
/usr/bin/bash
/usr/libexec/platform-python
config(candlepin) = 4.1.14-1.el8sat
java-11 >= 1:11.0.0
javapackages-tools
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
tomcatjss >= 7.2.1-7.1
wget



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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

root@satellite ~]# rpm -q --requires tomcatjss
apache-commons-lang3
java-1.8.0-openjdk-headless <-----------------
jpackage-utils >= 0:1.7.5-15
jss >= 4.9.0
jss < 5.0.0
pki-servlet-engine >= 1:9.0.7
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
slf4j
slf4j-jdk14


Expected results:

A similar java version or newer java should be used in the tomcatjss package. 


Additional info:

Comment 1 Chris Kelley 2022-11-17 12:00:55 UTC

I see that tomcatjss v7.2 is being used? This is now a very old version, the current version in RHEL 8.6 is v7.7.2.

Without seeing a full list of packages it is hard to say exactly what has happened but I would guess that you have a mix of old and new packages; some of which require Java 8 and some of which require Java 11. Can you please confirm this is the case? If it is, then this is non-standard configuration and there is nothing to be done so we can close the ticket.

Comment 2 Peter Vreman 2022-11-17 16:57:12 UTC

This is satellite 6.11.4 with candlepin 4.1 and using tomcatjss 7.7.1
as you can see even tomcatjss 7.7.1 is has a hardcoded requirement on java 1.8:
~~~
[cb/Azure] root@li-lc-2751:~# rpm -q satellite candlepin tomcatjss
satellite-6.11.4-2.el8sat.noarch
candlepin-4.1.14-1.el8sat.noarch
tomcatjss-7.7.1-1.module+el8.6.0+13291+248751b1.noarch
[cb/Azure] root@li-lc-2751:~# rpm -q --requires tomcatjss
apache-commons-lang3
java-1.8.0-openjdk-headless
jpackage-utils >= 0:1.7.5-15
jss >= 4.9.0
jss < 5.0.0
pki-servlet-engine >= 1:9.0.7
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
slf4j
slf4j-jdk14
[cb/Azure] root@li-lc-2751:~#
~~~

Comment 6 RHEL Program Management 2023-09-19 12:50:43 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 7 RHEL Program Management 2023-09-19 13:15:29 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.