You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Got this error from the log
2018/10/29 10:02:36 [error] 5801#5801: *96438 [lua] balancer.lua:174: balance(): error while setting current upstream peer [khaki.xxx.co.s3-website-ap-southeast-1.amazonaws.com]:80: invalid IPv6 address while connecting to upstream, client: 218.255.91.182, server: _, request: "GET /favicon.ico HTTP/1.1", host: "khaki.xxx.co", referrer: "http://khaki.xxx.co/"
I debugged to the lua code, and I found on balancer.lua that when the balancer is doing sync_backend(), the variable backend.service.spec is empty (which was supposed to include type and will then trigger a function to resolve the dns on external Name endpoint). Printing backend.service will show that spec is referring to a table address.
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG
NGINX Ingress controller version:
0.20.0
Kubernetes version (use
kubectl version
):Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.1", GitCommit:"d4ab47518836c750f9949b9e0d387f20fb92260b", GitTreeState:"clean", BuildDate:"2018-04-12T14:26:04Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.8", GitCommit:"7eab6a49736cc7b01869a15f9f05dc5b49efb9fc", GitTreeState:"clean", BuildDate:"2018-09-14T15:54:20Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Environment:
What happened:
Service type
externalName
is not resolved, resulting it to be wrapped as a ipv6 address instead of ipv4What you expected to happen:
Service type external name will then forward the request to intended address
How to reproduce it (as minimally and precisely as possible):
Ingress definition
Service definition
Anything else we need to know:
Got this error from the log
2018/10/29 10:02:36 [error] 5801#5801: *96438 [lua] balancer.lua:174: balance(): error while setting current upstream peer [khaki.xxx.co.s3-website-ap-southeast-1.amazonaws.com]:80: invalid IPv6 address while connecting to upstream, client: 218.255.91.182, server: _, request: "GET /favicon.ico HTTP/1.1", host: "khaki.xxx.co", referrer: "http://khaki.xxx.co/"
I debugged to the lua code, and I found on
balancer.lua
that when the balancer is doingsync_backend()
, the variablebackend.service.spec
is empty (which was supposed to include type and will then trigger a function to resolve the dns on external Name endpoint). Printingbackend.service
will show thatspec
is referring to a table address.But printing the content would result in nothing
This behavior may also be found on
ClusterIP
service that we have. It is strange since only some of these service don't have it.The text was updated successfully, but these errors were encountered: