Closed michalvavrik closed 1 week ago
run tests
run tests
Native failed over Caused by: java.security.cert.CertificateException: No subject alternative DNS name matching server.ts-jblpfaeiqm.svc.cluster.local found
which is the original reason why I added untilAsserted
. I think it is just flaky and we should add couple of seconds to waiting as it depends on OpenShift and not us. Let me add few seconds and retry.
run tests
yeah, OCP is green now so I'll merge it.
FYI: our weekly runs now fail due to : java.security.cert.CertificateException
FYI: our weekly runs now fail due to
: java.security.cert.CertificateException
thanks, I'll look. this seems like OCP setup or longer waiting, I don't know what could change in code to avoid this, but let see
in OpenShift they say that pod won't start until secret is mounted, so I think I need to inspect what is actually mounted in cases when it fails and whether it is retry or just randomness that is makes it sometimes fail and sometimes pass
it's not quite easy to reproduce, didn't happen to me once so far :-( maybe it is more likely to happen when OpenShift cluster is busy, don't know.
I figured it out: https://github.com/quarkus-qe/quarkus-test-framework/pull/1296
Summary
This is quite similar to what I have done in QE Test Framework https://github.com/quarkus-qe/quarkus-test-framework/pull/1270 because I think it tests all we need from TLS Registry integration with REST client and OpenShift certificate serving. Few differences:
Please select the relevant options.
run tests
phrase in comment)Checklist: