Skip to content
New issue

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

Issue 294 - java.net.UnknownHostException: pega-search-transport: Name or service not known #316

Merged
merged 4 commits into from
Jul 5, 2021

Conversation

Saurabh-16
Copy link
Contributor

. A single ES node was being launched and es-discovery appears to be trying to resolve the DNS before the pod is marked as Ready. The DNS from the stateless service is not being resolved as “Pod needs to become ready in order to have a record unless publishNotReadyAddresses=True is set on the Service.” (from https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/).

@MadhuriArugula MadhuriArugula added the integ-eks Label that triggers automation testing against EKS label Jun 28, 2021
@pegaautomationuser
Copy link
Collaborator

Starting PR-316 validation on -> integ-eks

1 similar comment
@pegaautomationuser
Copy link
Collaborator

Starting PR-316 validation on -> integ-eks

@pegaautomationuser
Copy link
Collaborator

Starting PR-316 validation on -> integ-eks

1 similar comment
@pegaautomationuser
Copy link
Collaborator

Starting PR-316 validation on -> integ-eks

@MadhuriArugula MadhuriArugula merged commit aec717a into pegasystems:master Jul 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
integ-eks Label that triggers automation testing against EKS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

java.net.UnknownHostException: pega-search-transport: Name or service not known
4 participants