dns_lookup(): failed to query the DNS server: no AAAA record resolved, context: ngx.timer error #9248
Comments
|
@marcandrews: This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
k8s-ci-robot
added
needs-triage
|
Version 0.28.0 is not supported. It's actually so old that it's not even
possible to debug it. Kindly upgrade to latest release and update status.
…On Wed, 2 Nov, 2022, 7:59 pm Kubernetes Prow Robot, < ***@***.***> wrote:
@marcandrews <https://github.com/marcandrews>: This issue is currently
awaiting triage.
If Ingress contributors determines this is a relevant issue, they will
accept it by applying the triage/accepted label and provide further
guidance.
The triage/accepted label can be added by org members by writing /triage
accepted in a comment.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository.
—
Reply to this email directly, view it on GitHub
<#9248 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGZVWUMRV6NVYDVDEWYTETWGJ3GHANCNFSM6AAAAAARVENAOE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
I figured as much 😄 I will upgrade this weekend and report back. |
|
/remove-kind bug
…On Wed, 2 Nov, 2022, 9:52 pm Marc Andrews, ***@***.***> wrote:
I figured as much 😄
I will upgrade this weekend and report back.
—
Reply to this email directly, view it on GitHub
<#9248 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGZVWQ76TRPAMF5AZVQVODWGKINPANCNFSM6AAAAAARVENAOE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
k8s-ci-robot
added
needs-kind
|
@longwuyuan I upgraded to v1.4.0 and I am still experiencing the issue. I noticed that nothing in my cluster is associated |
|
OK I think I figured it out. I ran [
{
"name": "custom-default-backend-default-****-api",
"service": {
"metadata": {
"creationTimestamp": null
},
"spec": {
"type": "ExternalName",
"sessionAffinity": "None",
"externalName": "storage.googleapis.com",
"internalTrafficPolicy": "Cluster"
},
"status": {
"loadBalancer": {}
}
},
"port": 80,
"sslPassthrough": false,
"endpoints": [
{
"address": "10.16.0.23",
"port": "6000"
},
{
"address": "10.16.4.23",
"port": "6000"
},
{
"address": "10.16.0.24",
"port": "6000"
},
{
"address": "10.16.4.24",
"port": "6000"
}
],
"sessionAffinityConfig": {
"name": "",
"mode": "",
"cookieSessionAffinity": {
"name": ""
}
},
"upstreamHashByConfig": {
"upstream-hash-by-subset-size": 3
},
"noServer": false,
"trafficShapingPolicy": {
"weight": 0,
"weightTotal": 0,
"header": "",
"headerValue": "",
"headerPattern": "",
"cookie": ""
}
},
...
]Then I looked at my ingresses and found that one of them had: metadata:
annotations:
...
nginx.ingress.kubernetes.io/default-backend: overlay-expert-apiOnce I removed that annotation, that backend no longer registered and the error no longer appears. The ingress in question is for the ExternalName service shown in the OP and I believe what I was trying to accomplish was to forward 404 originating from this ExternalName service to another service. After removing this annotation, the native Nginx 404 page is used. What's the best way to fallback to another service? (edit follow this maybe?) |
|
Yep, this is how to fallback to another service. Thanks @longwuyuan ❤️ |
What happened:
The
nginx-ingress-controllerappears to be functioning correctly, but is emitting these tens of thousands of these errors every hour:What you expected to happen:
I expect no errors to be emitted.
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
Kubernetes version (use
kubectl version):Environment:
Cloud provider or hardware configuration: GKE
OS (e.g. from /etc/os-release): n/a
Kernel (e.g.
uname -a): n/aInstall tools: Google Cloud Console
Basic cluster related info: n/a
How was the ingress-nginx-controller installed:
Current State of the controller:
kubectl describe ingressclasseskubectl -n <ingresscontrollernamespace> get all -A -o widekubectl -n <ingresscontrollernamespace> describe po <ingresscontrollerpodname>kubectl -n <ingresscontrollernamespace> describe svc <ingresscontrollerservicename>Current state of ingress object, if applicable:
kubectl -n <appnnamespace> get all,ing -o widekubectl -n <appnamespace> describe ing <ingressname>: n/aAnything else we need to know:
I have the following
ExternalNameservice:I followed this comment and it resolved #6060, but now I am experiencing this issue.
This issue might be related to #3882, #4551, #6523 and #8941.
I also realize that I am on an older version. I have been hesitant/scared to upgrade 😅 but will upgrading resolve the issue?
Any help will be greatly appreciated.
The text was updated successfully, but these errors were encountered: