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 1719014 - Expired certificate prevents tests from running
Summary: Expired certificate prevents tests from running
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lasso
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jakub Hrozek
QA Contact: Scott Poore
URL:
Whiteboard:
Depends On:
Blocks: 1719020
TreeView+ depends on / blocked
 
Reported: 2019-06-10 19:09 UTC by Jakub Hrozek
Modified: 2020-03-31 19:10 UTC (History)
2 users (show)

Fixed In Version: lasso-2.5.1-5.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1719020 (view as bug list)
Environment:
Last Closed: 2020-03-31 19:10:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1002 0 None None None 2020-03-31 19:10:24 UTC

Description Jakub Hrozek 2019-06-10 19:09:56 UTC 
Description of problem:
lasso's test suite includes a test (test13_test_lasso_server_load_metadata) which loads the signed XML metadata file and checks the signatures. But the documents are signed with a certificate that expired on Mar 23 09:51:37 2019.

This means that the upstream tests fail, which typically prevents the build from passing.

It is possible to just pass NULL instead of TESTSDATADIR "/metadata/metadata-federation-renater.crt" to the lasso_server_load_metadata() call in the test test13_test_lasso_server_load_metadata() which makes the test pass, but of course at the cost of some important code paths not being tested.

Unfortunately I can't think of any way of fixing or working around this short of upstream providing a new certificate (or us patching lasso with our own metadata signed by a cert we generate), but either way, we need to get a new cert somehow.

Version-Release number of selected component (if applicable):
lasso-2.5.1-3.el7

How reproducible:
always 

Steps to Reproduce:
1. rebuild the package
2.
3.

Actual results:
tests fail

Expected results:
tests pass

Additional info:
Upstream issue: https://dev.entrouvert.org/issues/33823
Comment 2 Jakub Hrozek 2019-06-11 08:39:54 UTC 
Fixed upstream in: https://dev.entrouvert.org/projects/lasso/repository/revisions/7c075657a4d64f4d8dbcd03521a0694287d5059f
Comment 3 Jakub Hrozek 2019-08-06 11:33:42 UTC 
Scott, would you mind adding a qa_ack here? Just verifying that the package built is enough, currently it does not because of this bug (example of a failed build: http://download.eng.bos.redhat.com/brewroot/work/tasks/2996/22922996/build.log)
Comment 5 Scott Poore 2019-10-22 20:55:19 UTC 
Verified Sanity Only.

Version:

lasso-2.5.1-5.el7.x86_64

Results:

I can see the fixed version built and installed which verifies that build time tests worked which did not before.

[root@sp1 ~]# rpm -q lasso
lasso-2.5.1-5.el7.x86_64

Also checking build log:

make[6]: Leaving directory `/builddir/build/BUILD/lasso-2.5.1/tests'
============================================================================
Testsuite summary for lasso 2.5.1
============================================================================
# TOTAL: 2
# PASS:  2
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0
============================================================================

...

make[8]: Leaving directory `/builddir/build/BUILD/lasso-2.5.1/bindings/python/tests'
============================================================================
Testsuite summary for lasso 2.5.1
============================================================================
# TOTAL: 2
# PASS:  2
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0
============================================================================
Comment 7 errata-xmlrpc 2020-03-31 19:10:19 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://access.redhat.com/errata/RHBA-2020:1002
Note You need to log in before you can comment on or make changes to this bug.