We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In https://github.com/jboss-openshift/openshift-ping/blob/main/server/src/main/java/org/openshift/ping/server/Utils.java there is no connection timeout used. In case the DNS name can be resolved but the target service IP can't be reached, this was failing the JBoss startup.
More details about this is available under: https://access.redhat.com/support/cases/#/case/01473052.
The text was updated successfully, but these errors were encountered:
Hi @pillimede ! Could you please have a look at the new upstream repository (https://github.com/jgroups-extras/jgroups-kubernetes) and check if this error still occurs? The code diverged a lot since last year so I'm not sure if it's still applicable.
If it does, please create an issue there (or let me know via email).
Sorry, something went wrong.
@pillimede I am getting 404 on the support case.
@rhusar @pillimede Yep, 404 for me as well.
But mainly, we need to see if this is somehow a problem with upstream implementation.
No branches or pull requests
In https://github.com/jboss-openshift/openshift-ping/blob/main/server/src/main/java/org/openshift/ping/server/Utils.java there is no connection timeout used. In case the DNS name can be resolved but the target service IP can't be reached, this was failing the JBoss startup.
More details about this is available under: https://access.redhat.com/support/cases/#/case/01473052.
The text was updated successfully, but these errors were encountered: