orangezhang123 opened a new issue, #1802:
URL: https://github.com/apache/apisix-ingress-controller/issues/1802
### Issue description
i upgrade apisix by helm ,this is the upgrade cmd:
helm upgrade apisix apisix/apisix --set gateway.type=LoadBalancer --set
admin.allow.ipList="{0.0.0.0/0}" --set etcd.persistence.storageClass="cbs"
--set etcd.persistence.size="20Gi" --namespace ingress-apisix --version
0.11.3
however,after i upgrade the apisix, the apisx pod 和apisix-ingress-controller
pod print the flowing error message:
apisx pod:
2023/04/19 07:59:25 [warn] 49#49: *893808 [lua] init.lua:164: handler():
stream mode is disabled, can not add any stream routes, client: 192.168.17.30,
server: , request: "GET /apisix/admin/stream_routes HTTP/1.1", host:
"apisix-admin.ingress-apisix.svc.cluster.local:9180"
2023/04/19 07:59:25 [warn] 49#49: *893808 [lua] init.lua:164: handler():
stream mode is disabled, can not add any stream routes, client: 192.168.17.30,
server: , request: "GET /apisix/admin/stream_routes HTTP/1.1", host:
"apisix-admin.ingress-apisix.svc.cluster.local:9180"
apisix-ingress-controller pod error message:
2023-04-19T16:03:18+08:00 [31merror[0m apisix/cluster.go:212 failed
to list routes in APISIX: Get
"http://apisix-admin.ingress-apisix.svc.cluster.local:9180/apisix/admin/routes":
context canceled
2023-04-19T16:03:18+08:00 [31merror[0m apisix/cluster.go:172 failed
to sync cache {"cost_time": "59.823µs", "cluster": "default"}
2023-04-19T16:03:18+08:00 [34minfo[0m ingress/controller.go:380
controller now is running as a candidate {"namespace": "ingress-apisix",
"pod": "apisix-ingress-controller-66fcc99f89-vnqdw"}
I0419 16:03:18.905856 1 leaderelection.go:248] attempting to acquire
leader lease ingress-apisix/ingress-apisix-leader...
2023-04-19T16:03:18+08:00 [34minfo[0m ingress/controller.go:328
LeaderElection {"message": "apisix-ingress-controller-66fcc99f89-vnqdw became
leader", "event_type": "Normal"}
I0419 16:03:18.912413 1 leaderelection.go:258] successfully acquired
lease ingress-apisix/ingress-apisix-leader
2023-04-19T16:03:18+08:00 [34minfo[0m ingress/controller.go:413
controller tries to leading ... {"namespace": "ingress-apisix", "pod":
"apisix-ingress-controller-66fcc99f89-vnqdw"}
2023-04-19T16:03:18+08:00 [34minfo[0m apisix/stream_route.go:39
resource stream_routes is disabled
2023-04-19T16:03:18+08:00 [33mwarn[0m apisix/cluster.go:334 waiting
cluster default to ready, it may takes a while
2023-04-19T16:03:18+08:00 [34minfo[0m apisix/cluster.go:374 syncing
schema {"cluster": "default"}
2023-04-19T16:03:18+08:00 [34minfo[0m apisix/cluster.go:162 syncing
cache {"cluster": "default"}
2023-04-19T16:03:18+08:00 [31merror[0m apisix/route.go:119 failed
to list routes: unexpected status code 404; error message: {"message":"Key not
found"}
2023-04-19T16:03:18+08:00 [31merror[0m apisix/cluster.go:212 failed
to list routes in APISIX: unexpected status code 404; error message:
{"message":"Key not found"}
2023-04-19T16:03:19+08:00 [34minfo[0m [email protected]/context.go:173
path: /healthz, status: 200, method: GET, query: , ip: 192.168.17.1,
user-agent: kube-probe/1.18+, errors: , cost: 36.458µs
2023-04-19T16:03:20+08:00 [31merror[0m apisix/route.go:119 failed
to list routes: unexpected status code 404; error message: {"message":"Key not
found"}
2023-04-19T16:03:20+08:00 [31merror[0m apisix/cluster.go:212 failed
to list routes in APISIX: unexpected status code 404; error message:
{"message":"Key not found"}
2023-04-19T16:03:22+08:00 [31merror[0m apisix/route.go:119 failed
to list routes: unexpected status code 404; error message: {"message":"Key not
found"}
2023-04-19T16:03:22+08:00 [31merror[0m apisix/cluster.go:212 failed
to list routes in APISIX: unexpected status code 404; error message:
{"message":"Key not found"}
2023-04-19T16:03:24+08:00 [31merror[0m apisix/route.go:119 failed
to list routes: unexpected status code 404; error message: {"message":"Key not
found"}
2023-04-19T16:03:24+08:00 [31merror[0m apisix/cluster.go:212 failed
to list routes in APISIX: unexpected status code 404; error message:
{"message":"Key not found"}
the etcd pod restart again and again
i search the github issue to help, and try to use
--set ingress-controller.enabled=true --set dashboard.enabled=true to
upgrade apisix again
but upgrade failed,here is the error message:
Error: UPGRADE FAILED: rendered manifests contain a resource that already
exists. Unable to continue with update: ServiceAccount "apisix-dashboard" in
namespace "ingress-apisix" exists and cannot be imported into the current
release: invalid ownership metadata; annotation validation error: key
"meta.helm.sh/release-name" must equal "apisix": current value is
"apisix-dashboard"
hope get help,thanks
### Environment
apisix version: 版本（tag）：3.2.0-debian
apisix-ingress-controller: 版本（tag）：1.5.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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
