You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/01/29 09:08:33 UTC
[GitHub] [apisix-ingress-controller] MirtoBusico opened a new issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
MirtoBusico opened a new issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851
### Issue description
I'm unable to define routes. But looking at the apisix ingress controller log I see these error:
```
2022-01-29T08:05:08.842Z | 2022-01-29T16:05:08+08:00 [31merror[0m apisix/plugin.go:46 failed to list plugins' names: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:05:08.842Z | 2022-01-29T16:05:08+08:00 [31merror[0m apisix/cluster.go:364 failed to list plugin names in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:05:08.842Z | 2022-01-29T16:05:08+08:00 [33mwarn[0m apisix/cluster.go:327 failed to sync schema: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:05:08.848Z | 2022-01-29T16:05:08+08:00 [34minfo[0m ingress/controller.go:290 LeaderElection {"message": "apisix-ingress-controller-7d5bbf5dd5-fhlz5 became leader", "event_type": "Normal"}
2022-01-29T08:05:08.848Z | I0129 16:05:08.848718 1 leaderelection.go:253] successfully acquired lease apisix/ingress-apisix-leader
2022-01-29T08:05:08.848Z | 2022-01-29T16:05:08+08:00 [34minfo[0m ingress/controller.go:370 controller tries to leading ... {"namespace": "apisix", "pod": "apisix-ingress-controller-7d5bbf5dd5-fhlz5"}
2022-01-29T08:05:08.848Z | 2022-01-29T16:05:08+08:00 [33mwarn[0m apisix/cluster.go:304 waiting cluster default to ready, it may takes a while
2022-01-29T08:05:09.398Z | [GIN] 2022/01/29 - 16:05:09 | 200 | 23.71µs | 127.0.0.6 | GET "/healthz"
2022-01-29T08:05:10.842Z | 2022-01-29T16:05:10+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:05:10.842Z | 2022-01-29T16:05:10+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
```
### Environment
- your apisix-ingress-controller version (output of apisix-ingress-controller version --long):
```
apache/apisix-ingress-controller:1.3.0 (taken from kubernetes dashboard)
```
- your Kubernetes cluster version (output of kubectl version):
```
sysop@m01serv:~$ kubectl version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.1", GitCommit:"86ec240af8cbd1b60bcc4c03c20da9b98005b92e", GitTreeState:"clean", BuildDate:"2021-12-16T11:41:01Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.5+k3s1", GitCommit:"405bf79da97831749733ad99842da638c8ee4802", GitTreeState:"clean", BuildDate:"2021-12-18T00:43:30Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"linux/amd64"}
sysop@m01serv:~$
```
- if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):
```
sysop@m01km:~$ uname -a
Linux m01km 5.4.0-96-generic #109-Ubuntu SMP Wed Jan 12 16:49:16 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
sysop@m01km:~$
(the OS of the kubernetes nodes hosting apisix)
```
### Minimal test code / Steps to reproduce
1) on a kubernetes cluster (using K3S) with Istio (and bookinfo demo application) installed, install Apisix with:
```
kubectl create ns apisix
kubectl label namespace apisix istio-injection=enabled
helm install apisix apisix/apisix \
--set gateway.type=NodePort \
--set ingress-controller.enabled=true \
--set ingress-controller.config.apisix.serviceNamespace=apisix \
--set ingress-controller.config.apisix.serviceName=apisix-admin \
--set dashboard.enabled=true \
--namespace apisix
```
Wait until all apisix resources are ready
2) try to create an Apisix route
Create a file named productpage-ar.yaml containing
```
apiVersion: apisix.apache.org/v2beta2
kind: ApisixRoute
metadata:
name: productpage
spec:
http:
- name: rule1
match:
hosts:
- www.m01.net
paths:
- /*
backends:
- serviceName: productpage
servicePort: 9080
```
Create the route with:
```
kubectl -n bookinfo apply -f productpage-ar.yaml
```
3) Verify that, for kubernetes, the route exist with:
```
sysop@m01serv:~$ kubectl describe apisixroute productpage -n bookinfo
Name: productpage
Namespace: bookinfo
Labels: <none>
Annotations: <none>
API Version: apisix.apache.org/v2beta2
Kind: ApisixRoute
Metadata:
Creation Timestamp: 2022-01-28T20:05:50Z
Generation: 1
Managed Fields:
API Version: apisix.apache.org/v2beta2
Fields Type: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.:
f:kubectl.kubernetes.io/last-applied-configuration:
f:spec:
.:
f:http:
Manager: kubectl-client-side-apply
Operation: Update
Time: 2022-01-28T20:05:50Z
Resource Version: 246403
UID: 9ffba506-71ce-4183-880a-290c44087c2e
Spec:
Http:
Backends:
Service Name: productpage
Service Port: 9080
Match:
Hosts:
www.m01.net
Paths:
/*
Name: rule1
Events: <none>
sysop@m01serv:~$
```
4) verify that the roure is not accessible (route not found error)
```
sysop@m01serv:~$ export NODE_PORT=$(kubectl get --namespace apisix -o jsonpath="{.spec.ports[0].nodePort}" services apisix-gateway)
sysop@m01serv:~$ export NODE_IP=$(kubectl get nodes --namespace apisix -o jsonpath="{.items[0].status.addresses[0].address}")
sysop@m01serv:~$ echo http://$NODE_IP:$NODE_PORT
http://192.168.102.121:30255
sysop@m01serv:~$ curl -I -H "HOST: www.m01.net" http://192.168.102.121:30255/
HTTP/1.1 404 Not Found
date: Sat, 29 Jan 2022 08:55:05 GMT
content-type: text/plain; charset=utf-8
server: istio-envoy
x-envoy-upstream-service-time: 0
x-envoy-decorator-operation: apisix-gateway.apisix.svc.cluster.local:80/*
transfer-encoding: chunked
sysop@m01serv:~$
```
5) Verify that in the apisix ingress controller pod there is the error "apisix/cluster.go:197 failed to list route"
```
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [31merror[0m apisix/plugin.go:46 failed to list plugins' names: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [31merror[0m apisix/cluster.go:364 failed to list plugin names in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [33mwarn[0m apisix/cluster.go:327 failed to sync schema: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:56:53.337Z | 2022-01-29T16:56:53+08:00 [34minfo[0m ingress/controller.go:290 LeaderElection {"message": "apisix-ingress-controller-7d5bbf5dd5-fhlz5 became leader", "event_type": "Normal"}
2022-01-29T08:56:53.337Z | I0129 16:56:53.337314 1 leaderelection.go:253] successfully acquired lease apisix/ingress-apisix-leader
2022-01-29T08:56:53.337Z | 2022-01-29T16:56:53+08:00 [34minfo[0m ingress/controller.go:370 controller tries to leading ... {"namespace": "apisix", "pod": "apisix-ingress-controller-7d5bbf5dd5-fhlz5"}
2022-01-29T08:56:53.337Z | 2022-01-29T16:56:53+08:00 [33mwarn[0m apisix/cluster.go:304 waiting cluster default to ready, it may takes a while
2022-01-29T08:56:53.786Z | [GIN] 2022/01/29 - 16:56:53 | 200 | 47.4µs | 127.0.0.6 | GET "/healthz"
```
### Actual result
Route not found
```
sysop@m01serv:~$ export NODE_PORT=$(kubectl get --namespace apisix -o jsonpath="{.spec.ports[0].nodePort}" services apisix-gateway)
sysop@m01serv:~$ export NODE_IP=$(kubectl get nodes --namespace apisix -o jsonpath="{.items[0].status.addresses[0].address}")
sysop@m01serv:~$ echo http://$NODE_IP:$NODE_PORT
http://192.168.102.121:30255
sysop@m01serv:~$ curl -I -H "HOST: www.m01.net" http://192.168.102.121:30255/
HTTP/1.1 404 Not Found
date: Sat, 29 Jan 2022 08:55:05 GMT
content-type: text/plain; charset=utf-8
server: istio-envoy
x-envoy-upstream-service-time: 0
x-envoy-decorator-operation: apisix-gateway.apisix.svc.cluster.local:80/*
transfer-encoding: chunked
sysop@m01serv:~$
```
### Error log
Error log from the apisix ingress controller pod
```
2022-01-29T08:56:21.328Z | 2022-01-29T16:56:21+08:00 [33mwarn[0m apisix/cluster.go:304 waiting cluster default to ready, it may takes a while
2022-01-29T08:56:23.324Z | 2022-01-29T16:56:23+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:23.324Z | 2022-01-29T16:56:23+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:23.787Z | [GIN] 2022/01/29 - 16:56:23 | 200 | 44.029µs | 127.0.0.6 | GET "/healthz"
2022-01-29T08:56:25.324Z | 2022-01-29T16:56:25+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:25.324Z | 2022-01-29T16:56:25+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:27.324Z | 2022-01-29T16:56:27+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:27.324Z | 2022-01-29T16:56:27+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:29.325Z | 2022-01-29T16:56:29+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:29.325Z | 2022-01-29T16:56:29+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:29.325Z | 2022-01-29T16:56:29+08:00 [31merror[0m apisix/cluster.go:164 failed to sync cache {"cost_time": "8.000909058s", "cluster": "default"}
2022-01-29T08:56:29.325Z | 2022-01-29T16:56:29+08:00 [31merror[0m ingress/controller.go:396 failed to wait the default cluster to be ready: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:29.325Z | 2022-01-29T16:56:29+08:00 [34minfo[0m ingress/controller.go:337 controller now is running as a candidate {"namespace": "apisix", "pod": "apisix-ingress-controller-7d5bbf5dd5-fhlz5"}
2022-01-29T08:56:29.325Z | I0129 16:56:29.325223 1 leaderelection.go:243] attempting to acquire leader lease apisix/ingress-apisix-leader...
2022-01-29T08:56:29.325Z | 2022-01-29T16:56:29+08:00 [34minfo[0m apisix/cluster.go:155 syncing cache {"cluster": "default"}
2022-01-29T08:56:29.325Z | 2022-01-29T16:56:29+08:00 [34minfo[0m apisix/cluster.go:344 syncing schema {"cluster": "default"}
2022-01-29T08:56:29.325Z | 2022-01-29T16:56:29+08:00 [31merror[0m apisix/plugin.go:46 failed to list plugins' names: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:56:29.325Z | 2022-01-29T16:56:29+08:00 [31merror[0m apisix/cluster.go:364 failed to list plugin names in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:56:29.325Z | 2022-01-29T16:56:29+08:00 [33mwarn[0m apisix/cluster.go:327 failed to sync schema: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:56:29.325Z | 2022-01-29T16:56:29+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:29.325Z | 2022-01-29T16:56:29+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:29.331Z | 2022-01-29T16:56:29+08:00 [34minfo[0m ingress/controller.go:290 LeaderElection {"message": "apisix-ingress-controller-7d5bbf5dd5-fhlz5 became leader", "event_type": "Normal"}
2022-01-29T08:56:29.331Z | I0129 16:56:29.331223 1 leaderelection.go:253] successfully acquired lease apisix/ingress-apisix-leader
2022-01-29T08:56:29.331Z | 2022-01-29T16:56:29+08:00 [34minfo[0m ingress/controller.go:370 controller tries to leading ... {"namespace": "apisix", "pod": "apisix-ingress-controller-7d5bbf5dd5-fhlz5"}
2022-01-29T08:56:29.331Z | 2022-01-29T16:56:29+08:00 [33mwarn[0m apisix/cluster.go:304 waiting cluster default to ready, it may takes a while
2022-01-29T08:56:29.399Z | [GIN] 2022/01/29 - 16:56:29 | 200 | 31.11µs | 127.0.0.6 | GET "/healthz"
2022-01-29T08:56:31.325Z | 2022-01-29T16:56:31+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:31.325Z | 2022-01-29T16:56:31+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:33.326Z | 2022-01-29T16:56:33+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:33.326Z | 2022-01-29T16:56:33+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:33.786Z | [GIN] 2022/01/29 - 16:56:33 | 200 | 33.32µs | 127.0.0.6 | GET "/healthz"
2022-01-29T08:56:35.326Z | 2022-01-29T16:56:35+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:35.326Z | 2022-01-29T16:56:35+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:37.326Z | 2022-01-29T16:56:37+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:37.326Z | 2022-01-29T16:56:37+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:37.326Z | 2022-01-29T16:56:37+08:00 [31merror[0m apisix/cluster.go:164 failed to sync cache {"cost_time": "8.001302695s", "cluster": "default"}
2022-01-29T08:56:37.326Z | 2022-01-29T16:56:37+08:00 [31merror[0m ingress/controller.go:396 failed to wait the default cluster to be ready: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:37.326Z | 2022-01-29T16:56:37+08:00 [34minfo[0m ingress/controller.go:337 controller now is running as a candidate {"namespace": "apisix", "pod": "apisix-ingress-controller-7d5bbf5dd5-fhlz5"}
2022-01-29T08:56:37.326Z | I0129 16:56:37.326764 1 leaderelection.go:243] attempting to acquire leader lease apisix/ingress-apisix-leader...
2022-01-29T08:56:37.326Z | 2022-01-29T16:56:37+08:00 [34minfo[0m apisix/cluster.go:155 syncing cache {"cluster": "default"}
2022-01-29T08:56:37.326Z | 2022-01-29T16:56:37+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:37.326Z | 2022-01-29T16:56:37+08:00 [34minfo[0m apisix/cluster.go:344 syncing schema {"cluster": "default"}
2022-01-29T08:56:37.326Z | 2022-01-29T16:56:37+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:37.327Z | 2022-01-29T16:56:37+08:00 [31merror[0m apisix/plugin.go:46 failed to list plugins' names: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:56:37.327Z | 2022-01-29T16:56:37+08:00 [31merror[0m apisix/cluster.go:364 failed to list plugin names in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:56:37.327Z | 2022-01-29T16:56:37+08:00 [33mwarn[0m apisix/cluster.go:327 failed to sync schema: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:56:37.332Z | 2022-01-29T16:56:37+08:00 [34minfo[0m ingress/controller.go:290 LeaderElection {"message": "apisix-ingress-controller-7d5bbf5dd5-fhlz5 became leader", "event_type": "Normal"}
2022-01-29T08:56:37.332Z | I0129 16:56:37.332392 1 leaderelection.go:253] successfully acquired lease apisix/ingress-apisix-leader
2022-01-29T08:56:37.332Z | 2022-01-29T16:56:37+08:00 [34minfo[0m ingress/controller.go:370 controller tries to leading ... {"namespace": "apisix", "pod": "apisix-ingress-controller-7d5bbf5dd5-fhlz5"}
2022-01-29T08:56:37.332Z | 2022-01-29T16:56:37+08:00 [33mwarn[0m apisix/cluster.go:304 waiting cluster default to ready, it may takes a while
2022-01-29T08:56:39.327Z | 2022-01-29T16:56:39+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:39.327Z | 2022-01-29T16:56:39+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:39.399Z | [GIN] 2022/01/29 - 16:56:39 | 200 | 31.55µs | 127.0.0.6 | GET "/healthz"
2022-01-29T08:56:41.327Z | 2022-01-29T16:56:41+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:41.327Z | 2022-01-29T16:56:41+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:43.327Z | 2022-01-29T16:56:43+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:43.327Z | 2022-01-29T16:56:43+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:43.786Z | [GIN] 2022/01/29 - 16:56:43 | 200 | 47.29µs | 127.0.0.6 | GET "/healthz"
2022-01-29T08:56:45.327Z | 2022-01-29T16:56:45+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:45.327Z | 2022-01-29T16:56:45+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:45.327Z | 2022-01-29T16:56:45+08:00 [31merror[0m apisix/cluster.go:164 failed to sync cache {"cost_time": "8.000914828s", "cluster": "default"}
2022-01-29T08:56:45.327Z | 2022-01-29T16:56:45+08:00 [31merror[0m ingress/controller.go:396 failed to wait the default cluster to be ready: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:45.327Z | 2022-01-29T16:56:45+08:00 [34minfo[0m ingress/controller.go:337 controller now is running as a candidate {"namespace": "apisix", "pod": "apisix-ingress-controller-7d5bbf5dd5-fhlz5"}
2022-01-29T08:56:45.327Z | I0129 16:56:45.327952 1 leaderelection.go:243] attempting to acquire leader lease apisix/ingress-apisix-leader...
2022-01-29T08:56:45.328Z | 2022-01-29T16:56:45+08:00 [34minfo[0m apisix/cluster.go:155 syncing cache {"cluster": "default"}
2022-01-29T08:56:45.328Z | 2022-01-29T16:56:45+08:00 [34minfo[0m apisix/cluster.go:344 syncing schema {"cluster": "default"}
2022-01-29T08:56:45.328Z | 2022-01-29T16:56:45+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:45.328Z | 2022-01-29T16:56:45+08:00 [31merror[0m apisix/plugin.go:46 failed to list plugins' names: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:56:45.328Z | 2022-01-29T16:56:45+08:00 [31merror[0m apisix/cluster.go:364 failed to list plugin names in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:56:45.328Z | 2022-01-29T16:56:45+08:00 [33mwarn[0m apisix/cluster.go:327 failed to sync schema: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:56:45.328Z | 2022-01-29T16:56:45+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:45.334Z | 2022-01-29T16:56:45+08:00 [34minfo[0m ingress/controller.go:290 LeaderElection {"message": "apisix-ingress-controller-7d5bbf5dd5-fhlz5 became leader", "event_type": "Normal"}
2022-01-29T08:56:45.334Z | I0129 16:56:45.334679 1 leaderelection.go:253] successfully acquired lease apisix/ingress-apisix-leader
2022-01-29T08:56:45.334Z | 2022-01-29T16:56:45+08:00 [34minfo[0m ingress/controller.go:370 controller tries to leading ... {"namespace": "apisix", "pod": "apisix-ingress-controller-7d5bbf5dd5-fhlz5"}
2022-01-29T08:56:45.334Z | 2022-01-29T16:56:45+08:00 [33mwarn[0m apisix/cluster.go:304 waiting cluster default to ready, it may takes a while
2022-01-29T08:56:47.328Z | 2022-01-29T16:56:47+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:47.328Z | 2022-01-29T16:56:47+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:49.328Z | 2022-01-29T16:56:49+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:49.328Z | 2022-01-29T16:56:49+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:49.399Z | [GIN] 2022/01/29 - 16:56:49 | 200 | 35.049µs | 127.0.0.6 | GET "/healthz"
2022-01-29T08:56:51.328Z | 2022-01-29T16:56:51+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:51.328Z | 2022-01-29T16:56:51+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [31merror[0m apisix/cluster.go:164 failed to sync cache {"cost_time": "8.001004415s", "cluster": "default"}
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [31merror[0m ingress/controller.go:396 failed to wait the default cluster to be ready: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [34minfo[0m ingress/controller.go:337 controller now is running as a candidate {"namespace": "apisix", "pod": "apisix-ingress-controller-7d5bbf5dd5-fhlz5"}
2022-01-29T08:56:53.329Z | I0129 16:56:53.329161 1 leaderelection.go:243] attempting to acquire leader lease apisix/ingress-apisix-leader...
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [34minfo[0m apisix/cluster.go:155 syncing cache {"cluster": "default"}
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [34minfo[0m apisix/cluster.go:344 syncing schema {"cluster": "default"}
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [31merror[0m apisix/plugin.go:46 failed to list plugins' names: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [31merror[0m apisix/cluster.go:364 failed to list plugin names in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:56:53.329Z | 2022-01-29T16:56:53+08:00 [33mwarn[0m apisix/cluster.go:327 failed to sync schema: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-29T08:56:53.337Z | 2022-01-29T16:56:53+08:00 [34minfo[0m ingress/controller.go:290 LeaderElection {"message": "apisix-ingress-controller-7d5bbf5dd5-fhlz5 became leader", "event_type": "Normal"}
2022-01-29T08:56:53.337Z | I0129 16:56:53.337314 1 leaderelection.go:253] successfully acquired lease apisix/ingress-apisix-leader
2022-01-29T08:56:53.337Z | 2022-01-29T16:56:53+08:00 [34minfo[0m ingress/controller.go:370 controller tries to leading ... {"namespace": "apisix", "pod": "apisix-ingress-controller-7d5bbf5dd5-fhlz5"}
2022-01-29T08:56:53.337Z | 2022-01-29T16:56:53+08:00 [33mwarn[0m apisix/cluster.go:304 waiting cluster default to ready, it may takes a while
2022-01-29T08:56:53.786Z | [GIN] 2022/01/29 - 16:56:53 | 200 | 47.4µs | 127.0.0.6 | GET "/healthz"
```
### Expected result
The route was found and the HTML return code is 200
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] apit commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
apit commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1026476314
thx @gamer22026, it's working now.
shouldn't apisix chart's values.yaml lists all configurations default? just like `config-default.yaml` in this repo?
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 edited a comment on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
tao12345666333 edited a comment on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1026944206
Thanks all. <s>Let me fix the APISIX helm chart configuration </s>
UPDATE: I think there are two problems here:
* Default behavior of APISIX
* When the APISIX Ingress controller synchronizes data, it is expected that all resources can be successfully synchronized (in this issue, resources such as stream_routes will inevitably fail because stream_proxy is not configured, but APISIX Ingress congtroller does not handle this situation. It's a bug.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] xianshun163 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
xianshun163 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1050720874
@tao12345666333 I have update the version to 1.4
that is a err log like this :
2022-02-25T18:11:17+08:00 error apisix/upstream.go:156 failed to create upstream: Put "http://apisix-gw-lb.default.svc.cluster.local:9080/apisix/admin/upstreams/db067616": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
2022-02-25T18:11:19+08:00 error apisix/upstream.go:76 failed to get upstream from APISIX {"name": "default_xsapp-service_80", "url": "http://apisix-gw-lb.default.svc.cluster.local:9080/apisix/admin/upstreams/db067616", "cluster": "default", "error": "Get \"http://apisix-gw-lb.default.svc.cluster.local:9080/apisix/admin/upstreams/db067616\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"}
2022-02-25T18:11:19+08:00 error ingress/apisix_upstream.go:151 failed to get upstream default_xsapp-service_80: Get "http://apisix-gw-lb.default.svc.cluster.local:9080/apisix/admin/upstreams/db067616": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
[GIN] 2022/02/25 - 18:11:19 | 200 | 118.307µs | 172.16.11.15 | GET "/healthz"
2022-02-25T18:11:22+08:00 error apisix/route.go:164 failed to create route: Put "http://apisix-gw-lb.default.svc.cluster.local:9080/apisix/admin/routes/8215ff3a": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
my upstream yaml file like this:
apiVersion: apisix.apache.org/v2beta3
kind: ApisixUpstream
metadata:
name: xsapp-service
spec:
timeout:
connect: 1s
read: 3s
send: 3s
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1024902073
Thanks！ let me check
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] MirtoBusico commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
MirtoBusico commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1026790597
The @gamer22026 suggestion worked for me.
The step I followed:
1) create the namespace
```
kubectl create ns apisix
kubectl label namespace apisix istio-injection=enabled
```
2) get the apisix chart values
```
helm show values apisix/apisix > apisix-values.yaml
```
3) change the lines 115-123 and 355-360
```
...
stream: # L4 proxy (TCP/UDP)
enabled: true
only: false
tcp: # TCP proxy address list
- 9100
- "127.0.0.1:9101"
udp: # UDP proxy address list
- 9200
- "127.0.0.1:9211"
...
dashboard:
enabled: true
ingress-controller:
enabled: true
```
4) installed with:
```
helm install apisix apisix/apisix -f apisix-values.yaml \
--set ingress-controller.config.apisix.serviceNamespace=apisix \
--set ingress-controller.config.apisix.serviceName=apisix-admin \
--namespace apisix
```
Now there is no error and I can define routes
I can also view the route defined in the dashboard.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1050652061
> @tao12345666333 is this problem fix? I have the same err, I use the 1.3 version.
Yes. It has been fixed. Please using latest Helm chart (APISIX Ingress v1.4
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1026944206
Thanks all. Let me fix the APISIX helm chart configuration
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] apit commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
apit commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1025055481
using ingress-controller 0.9 (v1.4) with apisix 0.8 (v2.12.0) still produced error
```log
2022-01-30T10:40:49+08:00 info ingress/ingress.go:112 apisix ingress controller started
2022-01-30T10:40:49+08:00 info ingress/ingress.go:114 version:
Version: 1.4.0
Git SHA: no-git-module
Go Version: go1.16.12
Building OS/Arch: linux/amd64
Running OS/Arch: linux/amd64
... /snip
2022-01-30T10:42:25+08:00 info apisix/cluster.go:370 syncing schema {"cluster": "default"}
2022-01-30T10:42:25+08:00 info apisix/cluster.go:158 syncing cache {"cluster": "default"}
2022-01-30T10:42:25+08:00 error apisix/plugin.go:46 failed to list plugins' names: Get "http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list": context canceled
2022-01-30T10:42:25+08:00 error apisix/cluster.go:390 failed to list plugin names in APISIX: Get "http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list": context canceled
2022-01-30T10:42:25+08:00 error apisix/cluster.go:353 failed to sync schema: Get "http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list": context canceled
2022-01-30T10:42:25+08:00 error apisix/route.go:119 failed to list routes: Get "http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes": context canceled
2022-01-30T10:42:25+08:00 error apisix/cluster.go:208 failed to list routes in APISIX: Get "http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes": context canceled
2022-01-30T10:42:25+08:00 error apisix/cluster.go:168 failed to sync cache {"cost_time": "37.754µs", "cluster": "default"}
E0130 10:42:25.818012 1 leaderelection.go:330] error retrieving resource lock apisix/ingress-apisix-leader: Get "https://10.43.0.1:443/apis/coordination.k8s.io/v1/namespaces/apisix/leases/ingress-apisix-leader": context canceled
2022-01-30T10:42:25+08:00 info ingress/controller.go:320 LeaderElection {"message": "apisix-ingress-controller-6846db58b8-np95n stopped leading", "event_type": "Normal"}
I0130 10:42:25.818041 1 leaderelection.go:283] failed to renew lease apisix/ingress-apisix-leader: timed out waiting for the condition
2022-01-30T10:42:25+08:00 info ingress/controller.go:372 controller now is running as a candidate {"namespace": "apisix", "pod": "apisix-ingress-controller-6846db58b8-np95n"}
I0130 10:42:25.818082 1 leaderelection.go:248] attempting to acquire leader lease apisix/ingress-apisix-leader...
2022-01-30T10:42:25+08:00 info ingress/controller.go:320 LeaderElection {"message": "apisix-ingress-controller-6846db58b8-np95n became leader", "event_type": "Normal"}
I0130 10:42:25.823238 1 leaderelection.go:258] successfully acquired lease apisix/ingress-apisix-leader
2022-01-30T10:42:25+08:00 info ingress/controller.go:409 controller tries to leading ... {"namespace": "apisix", "pod": "apisix-ingress-controller-6846db58b8-np95n"}
2022-01-30T10:42:25+08:00 warn apisix/cluster.go:330 waiting cluster default to ready, it may takes a while
2022-01-30T10:42:25+08:00 info apisix/cluster.go:370 syncing schema {"cluster": "default"}
2022-01-30T10:42:25+08:00 info apisix/cluster.go:158 syncing cache {"cluster": "default"}
2022-01-30T10:42:25+08:00 error apisix/stream_route.go:117 failed to list stream_routes: unexpected status code 400; error message: {"error_msg":"stream mode is disabled, can not add stream routes"}
```
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] apit commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
apit commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1025061489
no changes
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] gamer22026 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
gamer22026 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1026306420
If you are running apisix 2.12.0, I found that even though [this doc](https://github.com/apache/apisix/blob/master/docs/en/latest/stream-proxy.md#how-to-enable-stream-proxy) says that stream_proxy is configured if **_enable_admin: true_** it appears it does not. I added the snippet from the doc:
```
apisix:
stream_proxy: # TCP/UDP proxy
tcp: # TCP proxy address list
- 9100
- "127.0.0.1:9101"
udp: # UDP proxy address list
- 9200
- "127.0.0.1:9211"
```
and once I restarted apisix, the ingress-controller also started working and those errors went away.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] xianshun163 removed a comment on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
xianshun163 removed a comment on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1050777081
My apisix version is v1.11 .
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] MirtoBusico commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
MirtoBusico commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1024966366
**UPDATE**
I tried (in this order)
- delete apisix pod
- delete apisix-ingrass-controller
After this operation the apisix-ingress-controller log is:
```
2022-01-30T02:46:25+08:00 [34minfo[0m ingress/ingress.go:112 apisix ingress controller started
2022-01-30T02:46:25+08:00 [34minfo[0m ingress/ingress.go:114 version:
Version: 1.3.0
Git SHA: no-git-module
Go Version: go1.13.8
Building OS/Arch: linux/amd64
Running OS/Arch: linux/amd64
2022-01-30T02:46:25+08:00 [34minfo[0m ingress/ingress.go:120 use configuration
{
"cert_file": "/etc/webhook/certs/cert.pem",
"key_file": "/etc/webhook/certs/key.pem",
"log_level": "info",
"log_output": "stderr",
"http_listen": ":8080",
"https_listen": ":8443",
"enable_profiling": true,
"kubernetes": {
"kubeconfig": "",
"resync_interval": "6h0m0s",
"app_namespaces": [
""
],
"election_id": "ingress-apisix-leader",
"ingress_class": "apisix",
"ingress_version": "networking/v1",
"watch_endpoint_slices": false,
"apisix_route_version": "apisix.apache.org/v2beta1"
},
"apisix": {
"default_cluster_name": "default",
"default_cluster_base_url": "http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin",
"default_cluster_admin_key": "edd1c9f034335f136f87ad84b625c8f1",
"base_url": "http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin",
"admin_key": "edd1c9f034335f136f87ad84b625c8f1"
}
}
2022-01-30T02:46:25+08:00 [33mwarn[0m api/server.go:71 failed to load x509 key pair, will not start admission server {"Error": "open /etc/webhook/certs/cert.pem: no such file or directory", "CertFilePath": "/etc/webhook/certs/cert.pem", "KeyFilePath": "/etc/webhook/certs/key.pem"}
I0130 02:46:25.350705 1 leaderelection.go:243] attempting to acquire leader lease apisix/ingress-apisix-leader...
E0130 02:46:25.350976 1 leaderelection.go:325] error retrieving resource lock apisix/ingress-apisix-leader: Get https://10.43.0.1:443/apis/coordination.k8s.io/v1/namespaces/apisix/leases/ingress-apisix-leader: dial tcp 10.43.0.1:443: connect: connection refused
[GIN] 2022/01/30 - 02:46:27 | 200 | 152.769µs | 127.0.0.6 | GET "/healthz"
2022-01-30T02:46:28+08:00 [33mwarn[0m ingress/controller.go:328 found a new leader apisix-ingress-controller-7d5bbf5dd5-br7gn
2022-01-30T02:46:28+08:00 [34minfo[0m ingress/controller.go:330 controller now is running as a candidate {"namespace": "apisix", "pod": "apisix-ingress-controller-7d5bbf5dd5-9pcg7"}
[GIN] 2022/01/30 - 02:46:31 | 200 | 57.63µs | 127.0.0.6 | GET "/healthz"
[GIN] 2022/01/30 - 02:46:31 | 200 | 27.019µs | 127.0.0.6 | GET "/healthz"
[GIN] 2022/01/30 - 02:46:41 | 200 | 42.019µs | 127.0.0.6 | GET "/healthz"
[GIN] 2022/01/30 - 02:46:41 | 200 | 37.6µs | 127.0.0.6 | GET "/healthz"
2022-01-30T02:46:46+08:00 [34minfo[0m ingress/controller.go:290 LeaderElection {"message": "apisix-ingress-controller-7d5bbf5dd5-9pcg7 became leader", "event_type": "Normal"}
I0130 02:46:46.409605 1 leaderelection.go:253] successfully acquired lease apisix/ingress-apisix-leader
2022-01-30T02:46:46+08:00 [33mwarn[0m ingress/controller.go:328 found a new leader apisix-ingress-controller-7d5bbf5dd5-9pcg7
2022-01-30T02:46:46+08:00 [34minfo[0m ingress/controller.go:370 controller tries to leading ... {"namespace": "apisix", "pod": "apisix-ingress-controller-7d5bbf5dd5-9pcg7"}
2022-01-30T02:46:46+08:00 [33mwarn[0m apisix/cluster.go:304 waiting cluster default to ready, it may takes a while
2022-01-30T02:46:46+08:00 [34minfo[0m apisix/cluster.go:155 syncing cache {"cluster": "default"}
2022-01-30T02:46:46+08:00 [34minfo[0m apisix/cluster.go:344 syncing schema {"cluster": "default"}
2022-01-30T02:46:46+08:00 [31merror[0m apisix/stream_route.go:116 failed to list stream_routes: unexpected status code 400; error message: {"error_msg":"stream mode is disabled, can not add stream routes"}
2022-01-30T02:46:46+08:00 [31merror[0m apisix/cluster.go:212 failed to list stream_routes in APISIX: unexpected status code 400; error message: {"error_msg":"stream mode is disabled, can not add stream routes"}
```
Seems that nothing changes
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] xianshun163 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
xianshun163 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1050777081
My apisix version is v1.11 .
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] xianshun163 edited a comment on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
xianshun163 edited a comment on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1050730746
helm uninstall apisix-ingress-controller --namespace x
kubectl delete crd apisixclusterconfigs.apisix.apache.org
kubectl delete crd apisixconsumers.apisix.apache.org
kubectl delete crd apisixpluginconfigs.apisix.apache.org
kubectl delete crd apisixroutes.apisix.apache.org
kubectl delete crd apisixtlses.apisix.apache.org
kubectl delete crd apisixupstreams.apisix.apache.org
helm install apisix-ingress-controller apisix/apisix-ingress-controller --version=0.9.0 --namespace ingress-apisix --set config.kubernetes.ingressVersion=networking/v1beta1 \
--set config.apisix.serviceName=apisix-gw-lb --set config.apisix.serviceNamespace=default --set config.apisix.servicePort=9080 --set config.logLevel=warn --set config.apisix.adminKey=
I do it like this @tao12345666333
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] xianshun163 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
xianshun163 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1050773372
@tao12345666333 My apisix is not deploy by helm,I deploy it by docker images
Can you tell me which config to modify in the apisix, I do it myself
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] apit commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
apit commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1025059435
i cloned apisix-helm-chart repo, created apisix-ingress-controller-0.9.0.tgz, updated apisix Charts.yaml to use 0.9 and run this from on apisix chart folder,
```sh
helm install apisix . \
--insecure-skip-tls-verify \
--set gateway.type=NodePort \
--namespace apisix \
--set gateway.stream.enabled=true \
--set ingress-controller.enabled=true \
--set ingress-controller.config.apisix.serviceNamespace=apisix \
--set ingress-controller.config.apisix.serviceName=apisix-admin \
--set dashboard.enabled=true \
--set dashboard.config.apisix.serviceNamespace=apisix \
--kubeconfig k3s.yaml
```
i created an `ApisixRoute` but it doesn't shows up on ` kubectl exec -it -n apisix $(APISIX_POD) -- curl http://127.0.0.1:9180/apisix/admin/routes -H 'X-API-Key: mykey'`, and got previous log on the ingress pod.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] MirtoBusico commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
MirtoBusico commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1025126152
**UPDATE**
I reinstalled apisix from scratch and looked at the apisix-ingress-controller log before ever trying to create a route.
The pod is trapped in a loop between the "GET /healtz" messages
```
[GIN] 2022/01/30 - 19:41:39 | 200 | 35.789µs | 127.0.0.6 | GET "/healthz"
[GIN] 2022/01/30 - 19:41:39 | 200 | 819.067µs | 127.0.0.6 | GET "/healthz"
2022-01-30T19:41:41+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-30T19:41:41+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-30T19:41:43+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-30T19:41:43+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-30T19:41:45+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-30T19:41:45+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-30T19:41:45+08:00 [31merror[0m apisix/cluster.go:164 failed to sync cache {"cost_time": "8.000983025s", "cluster": "default"}
2022-01-30T19:41:45+08:00 [31merror[0m ingress/controller.go:396 failed to wait the default cluster to be ready: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-30T19:41:45+08:00 [34minfo[0m ingress/controller.go:337 controller now is running as a candidate {"namespace": "apisix", "pod": "apisix-ingress-controller-7d5bbf5dd5-4dr2m"}
I0130 19:41:45.428676 1 leaderelection.go:243] attempting to acquire leader lease apisix/ingress-apisix-leader...
2022-01-30T19:41:45+08:00 [34minfo[0m apisix/cluster.go:155 syncing cache {"cluster": "default"}
2022-01-30T19:41:45+08:00 [34minfo[0m apisix/cluster.go:344 syncing schema {"cluster": "default"}
2022-01-30T19:41:45+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-30T19:41:45+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-30T19:41:45+08:00 [31merror[0m apisix/plugin.go:46 failed to list plugins' names: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-30T19:41:45+08:00 [31merror[0m apisix/cluster.go:364 failed to list plugin names in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-30T19:41:45+08:00 [33mwarn[0m apisix/cluster.go:327 failed to sync schema: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/plugins/list: context canceled
2022-01-30T19:41:45+08:00 [34minfo[0m ingress/controller.go:290 LeaderElection {"message": "apisix-ingress-controller-7d5bbf5dd5-4dr2m became leader", "event_type": "Normal"}
I0130 19:41:45.432763 1 leaderelection.go:253] successfully acquired lease apisix/ingress-apisix-leader
2022-01-30T19:41:45+08:00 [34minfo[0m ingress/controller.go:370 controller tries to leading ... {"namespace": "apisix", "pod": "apisix-ingress-controller-7d5bbf5dd5-4dr2m"}
2022-01-30T19:41:45+08:00 [33mwarn[0m apisix/cluster.go:304 waiting cluster default to ready, it may takes a while
2022-01-30T19:41:47+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-30T19:41:47+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-30T19:41:49+08:00 [31merror[0m apisix/route.go:117 failed to list routes: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
2022-01-30T19:41:49+08:00 [31merror[0m apisix/cluster.go:197 failed to list route in APISIX: Get http://apisix-admin.apisix.svc.cluster.local:9180/apisix/admin/routes: context canceled
[GIN] 2022/01/30 - 19:41:49 | 200 | 31.261µs | 127.0.0.6 | GET "/healthz"
[GIN] 2022/01/30 - 19:41:49 | 200 | 35.169µs | 127.0.0.6 | GET "/healthz"
```
This loop is repeated continuously.
Hope this helps
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1050736476
The issue was fixed via the APISIX Helm chart. So what you did above won't fix the problem.
This problem is caused by stream_route being turned off in APISIX. Please refer to the comments in this issue to fix. Or use the latest APISIX Helm chart.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] xianshun163 edited a comment on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
xianshun163 edited a comment on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1050773372
@tao12345666333 My apisix is not deploy by helm,I deploy it by docker images
Can you tell me which config to modify in the apisix, I do it myself.
My apisix version is v1.11 .
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 closed issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
tao12345666333 closed issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] gamer22026 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
gamer22026 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1025951750
Same for me. Using latest 1.4.0
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] apit edited a comment on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
apit edited a comment on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1025059435
i cloned apisix-helm-chart repo, created apisix-ingress-controller-0.9.0.tgz and put that on apisix `charts` folder, updated apisix Charts.yaml to use 0.9 and run this from on apisix chart folder,
```sh
helm install apisix . \
--insecure-skip-tls-verify \
--set gateway.type=NodePort \
--namespace apisix \
--set gateway.stream.enabled=true \
--set ingress-controller.enabled=true \
--set ingress-controller.config.apisix.serviceNamespace=apisix \
--set ingress-controller.config.apisix.serviceName=apisix-admin \
--set dashboard.enabled=true \
--set dashboard.config.apisix.serviceNamespace=apisix \
--kubeconfig k3s.yaml
```
i created an `ApisixRoute` but it doesn't shows up on ` kubectl exec -it -n apisix $(APISIX_POD) -- curl http://127.0.0.1:9180/apisix/admin/routes -H 'X-API-Key: mykey'`, and got previous log on the ingress pod.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1025058167
@apit How did you deploy it?
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1035990645
> Thanks all. Let me fix the APISIX helm chart configuration
>
> UPDATE: I think there are two problems here:
>
> * Default behavior of APISIX
> * When the APISIX Ingress controller synchronizes data, it is expected that all resources can be successfully synchronized (in this issue, resources such as stream_routes will inevitably fail because stream_proxy is not configured, but APISIX Ingress congtroller does not handle this situation. It's a bug.
For the first of these I have fixed it in the Helm chart. This problem can be solved if you use the latest Helm chart. (chart version 0.8.2 ) https://github.com/apache/apisix-helm-chart/pull/233
For the second item, we can use #856 for tracking.
I will close this issue, thank you all.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1025060607
@apit if you restart(or delete) the apisix-ingress pod, does it work fine?
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1025041372
@MirtoBusico thanks for your report. I have found the problem it's due #769 and fixed in #774 （version v1.4）
We need update Helm chart version to using v1.4 apisix-ingress-controller
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] xianshun163 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
xianshun163 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1050650254
@tao12345666333 is this problem fix? I have the same err, I use the 1.3 version.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] xianshun163 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
xianshun163 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1050730746
helm uninstall apisix-ingress-controller --namespace x
kubectl delete crd apisixclusterconfigs.apisix.apache.org
kubectl delete crd apisixconsumers.apisix.apache.org
kubectl delete crd apisixpluginconfigs.apisix.apache.org
kubectl delete crd apisixroutes.apisix.apache.org
kubectl delete crd apisixtlses.apisix.apache.org
kubectl delete crd apisixupstreams.apisix.apache.org
helm install apisix-ingress-controller apisix/apisix-ingress-controller --version=0.9.0 --namespace ingress-apisix --set config.kubernetes.ingressVersion=networking/v1beta1 \
--set config.apisix.serviceName=apisix-gw-lb --set config.apisix.serviceNamespace=default --set config.apisix.servicePort=9080 --set config.logLevel=warn --set config.apisix.adminKey=
I do it like this
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1050729171
@xianshun163 Are you using the latest APISIX Helm chart? Or did you just upgrade the APISIX ingress? Please provide detailed steps.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #851: bug: Ingress controller error: apisix/route.go:117 failed to list routes
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #851:
URL: https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1050778947
https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1026306420
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org