This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2127210 - Older java 1.8 is still being needed on RHEL 8
Summary: Older java 1.8 is still being needed on RHEL 8
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: tomcatjss
Version: 8.6
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: RHCS Maintainers
QA Contact: idm-cs-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-15 17:19 UTC by Sahil Bhasin
Modified: 2023-09-19 13:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-19 13:15:29 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCS-3341 0 None None None 2022-10-20 07:01:08 UTC
Red Hat Issue Tracker   RHEL-5064 0 None Migrated None 2023-09-19 13:14:29 UTC
Red Hat Issue Tracker RHELPLAN-134087 0 None None None 2022-09-15 17:21:15 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.