Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionAleksandr Sharov
2020-09-10 10:09:21 UTC
Description of problem:
With installed latest krb5-libs-1.17-18.el8.x86_64, using Univa Grid Engine (uge formerly know as sge) on rhel8.2 doesn't work.
It works if krb5-libs is downgraded to krb5-libs-1.17-9.el8.x86_64.
Version-Release number of selected component (if applicable):
krb5-libs-1.17-18.el8.x86_64
Additional info:
details in case https://access.redhat.com/support/cases/02747159
Do we have an in-house reproducer for this issue?
In the non-working case, a non-system version of OpenSSL appears to be loaded:
openat(AT_FDCWD, "/opt/uge/8.6.12/bin/lx-amd64/../../lib/lx-amd64/libcrypto.so.1.1", O_RDONLY|O_CLOEXEC) = 3
Is it possible to reproduce the problem with the system OpenSSL version?
krb5-libs-1.17-18.el8.x86_64 loads libcrypto.so.1.1 from OpenSSL, while krb5-libs-1.17-9.el8.x86_64 does not. This explains why a downgrade krb5-libs appears to resolve the issue.
Comment 16Aleksandr Sharov
2020-09-16 09:52:54 UTC
Hi Florian!
Thank you for your explanation, but is there a way to make uge and krb5_libs coexist and don't utilise uge's libcrypto.so.1.1 ?
There's no sign of uge in ls.so.conf and none in LD_LIBRARY_PATH, DT_RPATH or DT_RUNPATH specified in the system, just general PATH and MANPATH and it's own variable:
[root@gotcentos8uge1t ~]# grep -i uge /etc/ld.so.conf* -r
[root@gotcentos8uge1t ~]# printenv | grep uge
SGE_ROOT=/opt/uge/default
MANPATH=/opt/uge/default/man:/usr/share/man:/usr/local/share/man
PATH=/opt/uge/default/bin/lx-amd64:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin
Thank you!
I don't know what “uge” is and how it works.
You could run the failing process with LD_DEBUG=all, to see if there are any dynamic linker diagnostics that show why it augments the search path in this way.