Bug 2032092 - Failing CSR Unit test due to expired test certificate
Summary: Failing CSR Unit test due to expired test certificate
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.z
Assignee: Damiano Donati
QA Contact: sunzhaohua
Depends On: 2031061
TreeView+ depends on / blocked
Reported: 2021-12-14 02:40 UTC by OpenShift BugZilla Robot
Modified: 2022-01-05 16:12 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-01-05 16:12:09 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-machine-approver pull 148 0 None open [release-4.8] Bug 2032092: Replace certificates with generated certificates 2021-12-14 09:22:08 UTC
Red Hat Product Errata RHBA-2021:5209 0 None None None 2022-01-05 16:12:15 UTC

Description OpenShift BugZilla Robot 2021-12-14 02:40:26 UTC
+++ This bug was initially created as a clone of Bug #2031061 +++

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

Description of problem:
The CSR Unit tests are failing due to an expired hard-coded certificate that we use in the test.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Check out master
2. Run tests
3. Observe tests failures due to expired certificate

Actual results:
Test fail

Expected results:
Test pass

Additional info:

Comment 2 sunzhaohua 2021-12-16 05:27:09 UTC
It's unit tests, move to verified.

Comment 6 errata-xmlrpc 2022-01-05 16:12:09 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 (OpenShift Container Platform 4.8.25 bug fix 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.


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