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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to