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 2021/04/15 09:14:46 UTC
[GitHub] [apisix-ingress-controller] pioneer-hash opened a new issue #379: bug: Synchronization configuration error when setting backends in route.yaml
pioneer-hash opened a new issue #379:
URL: https://github.com/apache/apisix-ingress-controller/issues/379
### Issue description
When I set backends in route.yaml, the synchronization configuration received an error ,Observation logs are a problem with the traffic-split plugin.
This is my yaml
```yaml
apiVersion: apisix.apache.org/v2alpha1
kind: ApisixRoute
metadata:
name: test-cookie-1
namespace: default
spec:
http:
- name: rule1
priority: 0
match:
paths:
- /*
backends:
- serviceName: web
servicePort: 80
- serviceName: web2
servicePort: 80
- name: rule2
priority: 2
match:
paths:
- /*
exprs:
- subject:
scope: Cookie
name: name
op: Equal
value: zhangsan
- subject:
scope: Header
name: name
op: NotEqual
value: lisi
backend:
serviceName: web1
servicePort: 80
```
this is error.log
```
2021-04-15T17:01:34+08:00 warn controller/apisix_route.go:205 sync ApisixRoute failed, will retry {"object": {"Type":1,"Object":{"Key":"default/test-cookie-1","OldObject":null,"GroupVersion":"apisix.apache.org/v2alpha1"},"Tombstone":null}, "error": "1 error occurred:\n\t* unexpected status code 400; error message: {\"error_msg\":\"unknown plugin [traffic-split]\"}\n\n\n"}
2021-04-15T17:02:34+08:00 error apisix/route.go:187 failed to create route: unexpected status code 400; error message: {"error_msg":"unknown plugin [traffic-split]"}
2021-04-15T17:02:34+08:00 warn controller/apisix_route.go:205 sync ApisixRoute failed, will retry {"object": {"Type":1,"Object":{"Key":"default/test-cookie-1","OldObject":null,"GroupVersion":"apisix.apache.org/v2alpha1"},"Tombstone":null}, "error": "1 error occurred:\n\t* unexpected status code 400; error message: {\"error_msg\":\"unknown plugin [traffic-split]\"}\n\n\n"}
```
### Environment
* your apisix-ingress-controller version (output of `apisix-ingress-controller version --long`);
apisix-ingress-controller version :0.5
apisix version : 2.5-centos
* 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`).
### Minimal test code / Steps to reproduce the issue
1.
2.
3.
### What's the actual result? (including assertion message & call stack if applicable)
### What's the expected result?
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #379: bug: Synchronization configuration error when setting backends in route.yaml
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #379:
URL: https://github.com/apache/apisix-ingress-controller/issues/379#issuecomment-822262286
@pioneer-hash Have you ever modified the APISIX 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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers closed issue #379: bug: Synchronization configuration error when setting backends in route.yaml
Posted by GitBox <gi...@apache.org>.
tokers closed issue #379:
URL: https://github.com/apache/apisix-ingress-controller/issues/379
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #379: bug: Synchronization configuration error when setting backends in route.yaml
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #379:
URL: https://github.com/apache/apisix-ingress-controller/issues/379#issuecomment-822987101
@pioneer-hash Please try the apisix helm chart `0.3.1`.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #379: bug: Synchronization configuration error when setting backends in route.yaml
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #379:
URL: https://github.com/apache/apisix-ingress-controller/issues/379#issuecomment-824647428
OK. Consider it was solved now.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #379: bug: Synchronization configuration error when setting backends in route.yaml
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #379:
URL: https://github.com/apache/apisix-ingress-controller/issues/379#issuecomment-822436756
@pioneer-hash It seems that the `traffic-split` plugin is not enabled in the current apisix helm chart release.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #379: bug: Synchronization configuration error when setting backends in route.yaml
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #379:
URL: https://github.com/apache/apisix-ingress-controller/issues/379#issuecomment-822437675
I have submitted a PR to fix this: https://github.com/apache/apisix-helm-chart/pull/63.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] pioneer-hash commented on issue #379: bug: Synchronization configuration error when setting backends in route.yaml
Posted by GitBox <gi...@apache.org>.
pioneer-hash commented on issue #379:
URL: https://github.com/apache/apisix-ingress-controller/issues/379#issuecomment-822271149
> @pioneer-hash Have you ever modified the APISIX configuration?
No,I just changed the name generic type of Chart.yaml
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] pioneer-hash commented on issue #379: bug: Synchronization configuration error when setting backends in route.yaml
Posted by GitBox <gi...@apache.org>.
pioneer-hash commented on issue #379:
URL: https://github.com/apache/apisix-ingress-controller/issues/379#issuecomment-824555698
> @pioneer-hash Please try the apisix helm chart `0.3.1`.
success!
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers closed issue #379: bug: Synchronization configuration error when setting backends in route.yaml
Posted by GitBox <gi...@apache.org>.
tokers closed issue #379:
URL: https://github.com/apache/apisix-ingress-controller/issues/379
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org