-
Bug
-
Resolution: Obsolete
-
Normal
-
None
-
4.13.z, 4.12.z, 4.11.z
-
Important
-
No
-
False
-
Description of problem:
a few e2e tests are failing due to a cert issue: [sig-auth][Feature:OAuthServer] [Token Expiration] Using a OAuth client with a non-default token max age [apigroup:oauth.openshift.io] to generate tokens that do not expire works as expected when using a token authorization flow [apigroup:user.openshift.io] [Suite:openshift/conformance/parallel] [sig-auth][Feature:OAuthServer] [Token Expiration] Using a OAuth client with a non-default token max age [apigroup:oauth.openshift.io] to generate tokens that expire shortly works as expected when using a token authorization flow [apigroup:user.openshift.io] [Suite:openshift/conformance/parallel] [sig-auth][Feature:HTPasswdAuth] HTPasswd IDP should successfully configure htpasswd and be responsive [apigroup:user.openshift.io][apigroup:route.openshift.io] [Suite:openshift/conformance/parallel]
Version-Release number of selected component (if applicable):
4.13.19
How reproducible:
create an on-prem cluster and run the e2e suite
Steps to Reproduce:
1. compile the openshift-tests binary from https://github.com/openshift/origin/tree/release-4.13/ 2. run the test suite
Actual results:
a handful of tests fail with "tls: failed to verify certificate: x509: certificate signed by unknown authority"
Expected results:
{code:none}
Additional info:
we're seeing this against IBM Power (ppc64le), but someone with access to an x86 cluster verified it fails in the same way there. It does *not* happen in any of the public CI jobs (for x86 or Power).