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 2070879 - krb5 upstream api tests failed [rhel-8.7.0]
Summary: krb5 upstream api tests failed [rhel-8.7.0]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: krb5
Version: 8.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Julien Rische
QA Contact: Filip Dvorak
URL:
Whiteboard:
Depends On: 2053133
Blocks: 2069077
TreeView+ depends on / blocked
 
Reported: 2022-04-01 09:24 UTC by Julien Rische
Modified: 2022-11-08 12:25 UTC (History)
1 user (show)

Fixed In Version: krb5-1.18.2-20.el8
Doc Type: No Doc Update
Doc Text:
Clone Of: 2053133
Environment:
Last Closed: 2022-11-08 10:45:40 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-8123 0 None None None 2022-04-01 09:42:46 UTC
Red Hat Issue Tracker RHELPLAN-117597 0 None None None 2022-04-01 09:43:08 UTC
Red Hat Product Errata RHBA-2022:7696 0 None None None 2022-11-08 10:46:09 UTC

Description Julien Rische 2022-04-01 09:24:16 UTC 
+++ This bug was initially created as a clone of Bug #2053133 +++

Description of problem:
krb5 upstream API tests failed.

Version-Release number of selected component (if applicable):
krb5-server-1.19.1-13.el9.x86_64
RHEL-9.0.0-20220127.4

Steps to Reproduce:
1. rpmbuild -bc $BUILDDIR/SPECS/krb5.spec
2. make check -C /root/rpmbuild/BUILD/krb5-1.19.1/src

Actual results:
...
making check in lib/kadm5/unit-test...
make[4]: Entering directory '/root/rpmbuild/BUILD/krb5-1.19.1/src/lib/kadm5/unit-test'
../../../kadmin/testing/scripts/env-setup.sh  ../../../kadmin/testing/scripts/start_servers
../../../kadmin/testing/scripts/env-setup.sh  ./init-test
../../../kadmin/testing/scripts/env-setup.sh  ./destroy-test
../../../kadmin/testing/scripts/env-setup.sh  ./client-handle-test
../../../kadmin/testing/scripts/env-setup.sh  ./client-setkey-test testkeys admin admin
+ Test 0:
+   enctype 17
+ Test 1:
+   enctype 17
+ Test 2:
+   enctype 17
../../../kadmin/testing/scripts/env-setup.sh runtest --debug --srcdir . --host x86_64-redhat-linux-gnu --tool api RPC=1 API=../../../kadmin/testing/util/kadm5_clnt_tcl \
        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 Thu Feb 10 14:10:47 2022
Native configuration is x86_64-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.
WARNING: Couldn't find tool config file for unix, using default.
WARNING: could not find testsuite; trying ..
Running ./api.2/crte-policy.exp ...
ERROR: Couldn't find library file lib.t.
make[4]: *** [Makefile:758: unit-test-client-body] Error 1
make[4]: Leaving directory '/root/rpmbuild/BUILD/krb5-1.19.1/src/lib/kadm5/unit-test'
make[3]: *** [Makefile:1115: check-recurse] Error 1
make[3]: Leaving directory '/root/rpmbuild/BUILD/krb5-1.19.1/src/lib/kadm5'
make[2]: *** [Makefile:1006: check-recurse] Error 1
make[2]: Leaving directory '/root/rpmbuild/BUILD/krb5-1.19.1/src/lib'
make[1]: *** [Makefile:1553: check-recurse] Error 1
make[1]: Leaving directory '/root/rpmbuild/BUILD/krb5-1.19.1/src'

Expected results:
upstream api tests should pass.

Additional info:
- tests passed with RHEL-9.0.0-20220111.1 but failed in RHEL-9.0.0-20220127.4

--- Additional comment from Julien Rische on 2022-03-03 17:14:28 UTC ---

Upstream tests are passing if run with dejagnu-1.6.1-13. The 1.6.3 rebase probably introduced some breaking changes:

https://gitlab.com/redhat/centos-stream/rpms/dejagnu/-/commit/8e2e7164870bee8489522cb17b840beb93c6fcab

--- Additional comment from Julien Rische on 2022-03-31 16:57:26 UTC ---

This problem is due to a newly enforced path naming convention in dejagnu[1].

I opened a C9S PR[2], renaming the kadm5 library's unit tests directory to fix this issue.

[1] https://www.mail-archive.com/bug-dejagnu@gnu.org/msg00366.html
[2] https://gitlab.com/redhat/centos-stream/rpms/krb5/-/merge_requests/14
Comment 14 errata-xmlrpc 2022-11-08 10:45:40 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 (krb5 bug fix and enhancement update), 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/RHBA-2022:7696
Note You need to log in before you can comment on or make changes to this bug.