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 1281348 - Upstream unit tests loads the installed shared libraries instead the ones from the build
Summary: Upstream unit tests loads the installed shared libraries instead the ones fro...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: krb5
Version: 6.8
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Robbie Harwood
QA Contact: Patrik Kis
URL: https://github.com/krb5/krb5/pull/340
Whiteboard:
Depends On:
Blocks: 1297591
TreeView+ depends on / blocked
 
Reported: 2015-11-12 11:03 UTC by Patrik Kis
Modified: 2017-03-21 10:03 UTC (History)
4 users (show)

Fixed In Version: krb5-1.10.3-62.el6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1164304
: 1297591 (view as bug list)
Environment:
Last Closed: 2017-03-21 10:03:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0643 0 normal SHIPPED_LIVE krb5 bug fix update 2017-03-21 12:31:52 UTC

Description Patrik Kis 2015-11-12 11:03:21 UTC
This problem also exists in RHEL-6.7 version of krb5. It remained unattended due to an error in our test.
Please fix it so we can be sure the intended version of krb5 is tested.

Affected version: krb5-1.10.3-45.el6

The crash mentioned in the original report was not seen, but the installed libraries are loaded according the audit logs. And the fix from upstream patch is also not present on the src of the test.

+++ This bug was initially created as a clone of Bug #1164304 +++

Description of problem:
krb5-1.12.2/src/lib/kadm5/unit-test fails (segfaults) when krb5-pkinit is installed on the sysytem.
Monitoring via audit showed that unit tests from this directory loads pkinit.so from the installed package and not the one that was built.
On top of that, monitoring showed that libs from the installed krb5-libs (whatever version installed) are loaded too.
This questions the effectiveness of upstream testing.

Version-Release number of selected component (if applicable):
krb5-libs-1.12.2-8.el7

How reproducible:
always

Steps to Reproduce:

# rpm -qa krb5\*
krb5-devel-1.11.3-49.el7.ppc64
krb5-libs-1.11.3-49.el7.ppc64
krb5-pkinit-1.11.3-49.el7.ppc64
#
# rpm -ivh krb5-1.12.2-8.el7.src.rpm 
... snip ...
# rpmbuild -bc ~/rpmbuild/SPECS/krb5.spec 
... snip ...
#
# cd ~/rpmbuild/BUILD/krb5-1.12.2/src/
# make runenv.py
LD_LIBRARY_PATH=`echo -L./lib | sed -e "s/-L//g" -e "s/ /:/g"`; export LD_LIBRARY_PATH;  \
for i in LD_LIBRARY_PATH; do \
	eval echo 'env['\\\'$i\\\''] = '\\\'\$$i\\\'; \
done > pyrunenv.vals
echo "proxy_tls_impl = 'openssl'" >> pyrunenv.vals
echo 'env = {}' > runenv.py
cat pyrunenv.vals >> runenv.py
# cd lib/kadm5/unit-test/
# make check
.. snip ...
	KINIT=../../../clients/kinit/kinit \
	KDESTROY=../../../clients/kdestroy/kdestroy \
	KADMIN_LOCAL=../../../kadmin/cli/kadmin.local \
	PRIOCNTL_HACK=0 VALGRIND="" \
	
WARNING: Couldn't find the global config file.
WARNING: Couldn't find tool init file
Test Run By root on Fri Nov 14 10:30:35 2014
Native configuration is powerpc64-redhat-linux-gnu

		=== api tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ./config/unix.exp as tool-and-target-specific interface file.
Running ./api.2/crte-policy.exp ...
FAIL: create-policy 1: eof
ERROR: create-policy 1: unexpected failure in init
ERROR: create-policy 2: unexpected failure in init
ERROR: create-policy 3: unexpected failure in init
kadmin/testing/proto/krb5.conf.proto

Comment 1 Robbie Harwood 2015-11-13 18:16:16 UTC
I (but mostly Greg) have made some changes on this front upstream, though they were for 1.14 and I have no idea how well they'll backport.

Comment 3 Patrik Kis 2015-11-16 11:55:47 UTC
(In reply to Robbie Harwood from comment #1)
> I (but mostly Greg) have made some changes on this front upstream, though
> they were for 1.14 and I have no idea how well they'll backport.

These 2 lines help for krb5-1.10.3 too:
https://github.com/krb5/krb5/pull/340/files
but I can imagine there was more robust fix at the end.

Comment 4 Robbie Harwood 2015-11-16 17:54:35 UTC
Indeed, that was my original attempt to fix the issue, but it turns out to run deeper.  The final fix was https://github.com/krb5/krb5/pull/341

Comment 13 errata-xmlrpc 2017-03-21 10:03:13 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://rhn.redhat.com/errata/RHBA-2017-0643.html


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