gaoxingliang opened a new issue, #1640:
URL: https://github.com/apache/apisix-ingress-controller/issues/1640
### Current Behavior
apisix ingress controller has a lot of errors, and it's always waiting a
cluster to be ready:
```
2023-02-01T17:42:38+08:00 error apisix/cluster.go:172 failed to sync
cache {"cost_time": "56.218µs", "cluster": "default"}
2023-02-01T17:42:38+08:00 info apisix/cluster.go:374 syncing schema
{"cluster": "default"}
2023-02-01T17:42:38+08:00 error apisix/plugin.go:46 failed to list
plugins' names: Get
"http://apisix-admin.apisix-gateway.svc.cluster.local:9180/apisix/admin/plugins?all=true":
context canceled
2023-02-01T17:42:38+08:00 error apisix/cluster.go:394 failed to list
plugin names in APISIX: Get
"http://apisix-admin.apisix-gateway.svc.cluster.local:9180/apisix/admin/plugins?all=true":
context canceled
2023-02-01T17:42:38+08:00 error apisix/cluster.go:357 failed to sync
schema: Get
"http://apisix-admin.apisix-gateway.svc.cluster.local:9180/apisix/admin/plugins?all=true":
context canceled
2023-02-01T17:42:38+08:00 info ingress/controller.go:380
controller now is running as a candidate {"namespace": "apisix-gateway",
"pod": "apisix-ingress-controller-75569f88cc-kdjck"}
I0201 17:42:38.554368 1 leaderelection.go:248] attempting to acquire
leader lease apisix-gateway/ingress-apisix-leader...
2023-02-01T17:42:38+08:00 info ingress/controller.go:328
LeaderElection {"message": "apisix-ingress-controller-75569f88cc-kdjck became
leader", "event_type": "Normal"}
I0201 17:42:38.557741 1 leaderelection.go:258] successfully acquired
lease apisix-gateway/ingress-apisix-leader
2023-02-01T17:42:38+08:00 info ingress/controller.go:413
controller tries to leading ... {"namespace": "apisix-gateway", "pod":
"apisix-ingress-controller-75569f88cc-kdjck"}
2023-02-01T17:42:38+08:00 info apisix/stream_route.go:39
resource stream_routes is disabled
2023-02-01T17:42:38+08:00 warn apisix/cluster.go:334 waiting cluster
default to ready, it may takes a while
2023-02-01T17:42:38+08:00 info apisix/cluster.go:374 syncing schema
{"cluster": "default"}
2023-02-01T17:42:38+08:00 info apisix/cluster.go:162 syncing cache
{"cluster": "default"}
2023-02-01T17:42:38+08:00 error apisix/ssl.go:114 failed to list
ssl: unexpected status code 404; error message: {"error_msg":"not found"}
2023-02-01T17:42:38+08:00 error apisix/cluster.go:222 failed to list
ssl in APISIX: unexpected status code 404; error message: {"error_msg":"not
found"}
2023-02-01T17:42:40+08:00 error apisix/ssl.go:114 failed to list
ssl: unexpected status code 404; error message: {"error_msg":"not found"}
2023-02-01T17:42:40+08:00 error apisix/cluster.go:222 failed to list
ssl in APISIX: unexpected status code 404; error message: {"error_msg":"not
found"}
2023-02-01T17:42:42+08:00 error apisix/ssl.go:114 failed to list
ssl: unexpected status code 404; error message: {"error_msg":"not found"}
2023-02-01T17:42:42+08:00 error apisix/cluster.go:222 failed to list
ssl in APISIX: unexpected status code 404; error message: {"error_msg":"not
found"}
```
### Expected Behavior
_No response_
### Error Logs
_No response_
### Steps to Reproduce
1. See above error logs
### Environment
- APISIX version (run `apisix version`): 3.1.0
- Operating system (run `uname -a`):
- OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
- etcd version, if relevant (run `curl
http://127.0.0.1:9090/v1/server_info`):
- APISIX Dashboard version, if relevant:
- Plugin runner version, for issues related to plugin runners:
- LuaRocks version, for installation issues (run `luarocks --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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
