Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

request help: traffic-split 插件提示错误 #2293

Closed
wxqmail opened this issue Sep 6, 2024 · 2 comments
Closed

request help: traffic-split 插件提示错误 #2293

wxqmail opened this issue Sep 6, 2024 · 2 comments
Labels

Comments

@wxqmail
Copy link

wxqmail commented Sep 6, 2024

Issue description

apisix版本 2.15
controller 版本 1.8.0
k8s 版本 1.26
apisix 集群是独立部署(部署了3个节点), 非k8s内部署
应用的部署控制使用了argo-rollout 的金丝雀部署功能
一些路由会出现以下错误, 每次出现时只要把 controller 重启就能恢复正常

错误日志:
2024/09/06 09:21:10 [error] 373320#373320: *19527373058 lua entry thread aborted: runtime error: /data/www/gateway_apisix/apisix/plugins/traffic-split.lua:205: attempt to index field 'upstream' (a string value)
stack traceback:
coroutine 0:
/data/www/gateway_apisix/apisix/plugins/traffic-split.lua: in function 'create_obj_fun'
/data/www/gateway_apisix/apisix/core/lrucache.lua:95: in function 'lrucache'
/data/www/gateway_apisix/apisix/plugins/traffic-split.lua:267: in function 'phase_func'
/data/www/gateway_apisix/apisix/plugin.lua:934: in function 'run_plugin'
/data/www/gateway_apisix/apisix/init.lua:461: in function 'http_access_phase'
access_by_lua(nginx.conf:329):2: in main chunk, client: 223.72.83.215, server: _, request: "POST /dma/de HTTP/2.0", host: "app.xxxxx.com", referrer: "https://app.xxxxx.com/"

Environment

  • your apisix-ingress-controller version (output of apisix-ingress-controller version --long):
  • your Kubernetes cluster version (output of kubectl version):
  • if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):
Copy link

github-actions bot commented Dec 6, 2024

This issue has been marked as stale due to 90 days of inactivity. It will be closed in 30 days if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the [email protected] list. Thank you for your contributions.

@github-actions github-actions bot added the stale label Dec 6, 2024
Copy link

github-actions bot commented Jan 6, 2025

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.

@github-actions github-actions bot closed this as completed Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant