yesamer opened a new pull request, #2248:
URL: https://github.com/apache/incubator-kie-examples/pull/2248

   ## Problem
   
   `OnboardingEndpointIT` fails intermittently in CI with:
   
   
   ```
   io.vertx.core.VertxException: java.security.cert.CertificateException:
   No provider succeeded to generate a self-signed certificate.
   Caused by: java.lang.UnsupportedOperationException:
   OpenJdkSelfSignedCertGenerator not supported on the used JDK version
   ```
   
   
   The `@EnableKubernetesMockClient` annotation starts a `KubernetesMockServer`
   in HTTPS mode by default. To serve TLS, Netty's `SelfSignedCertificate` tries
   three certificate generators in sequence:
   
   | Provider | Result on JDK 17 |
   |---|---|
   | `OpenJdkSelfSignedCertGenerator` | Always fails — `sun.security.x509.*` 
blocked by JPMS strong encapsulation |
   | `BouncyCastleSelfSignedCertGenerator` | Always fails — BouncyCastle not on 
the classpath |
   | `KeytoolSelfSignedCertGenerator` | Intermittently fails — shells out to 
`keytool`, sensitive to runner environment |
   
   Because the first two providers are categorically broken on JDK 17, the 
entire
   reliability burden falls on the `keytool` fallback, which is sensitive to 
PATH
   propagation and ephemeral runner image changes — causing the non-systematic 
failure.
   
   ## Fix
   
   Add `https = false` to the `@EnableKubernetesMockClient` annotation.
   
   The mock server is only present so the `kie-addons-quarkus-kubernetes` 
extension
   has a Kubernetes API endpoint to connect to at application startup. The test 
itself
   exercises process execution over REST and has no dependency on the transport
   protocol used by the mock server. HTTP is fully sufficient.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to