-
Bug
-
Resolution: Done
-
Critical
-
7.2.0.GA, 7.3.0.CD15
-
None
-
-
-
-
-
-
Workaround Exists
-
On OCP 4.1 we are facing failing tests with error
Cluster did not join - pods: jgroups-1-jj7hc, jgroups-1-lflc6 in timeout: 120000 ms
All failing tests have in common this WARN occures in log
WARN [org.jgroups.protocols.openshift.KUBE_PING] (ServerService Thread Pool -- 77) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.TokenStreamProvider@73d58664] for cluster [ee], namespace [eap72-tests-suite], labels [null]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target]]
- There are no issues with other jgroups protocols.
- Tests are working fine on OCP 3.11.
- is caused by
-
CLOUD-3228 Legacy openshift.KUBE_PING doesn't work on OCP 4.1 since it only parses the first CA certificate from the ca.crt store
- New
- is related to
-
JBEAP-16949 Stale reference to "openshift.KUBE_PING" in docs
- Closed