wumengchao opened a new issue, #2071:
URL: https://github.com/apache/apisix-ingress-controller/issues/2071
### Current Behavior
Occasionally, changes to the routing configuration do not take effect, and
the deleted routing configurations are still active. At the same time, the
backend reports the following errors, and I am not sure if these errors are
related to this bug.
2023-11-25T04:31:57+08:00 [31merror[0m adapter/etcd.go:141 failed to
create object, ignore it{error 26 0 rpc error: code = InvalidArgument desc =
etcdserver: duplicate key given in txn request} {revision 11 26 <nil>} {key 15
0 /apisix/routes/6d611fe0 <nil>}
### Expected Behavior
_No response_
### Error Logs
2023-11-25T04:31:57+08:00 [31merror[0m adapter/etcd.go:141 failed to
create object, ignore it{error 26 0 rpc error: code = InvalidArgument desc =
etcdserver: duplicate key given in txn request} {revision 11 26 <nil>} {key 15
0 /apisix/routes/6d611fe0 <nil>}
### Steps to Reproduce
Deployed using the latest version 1.7.1, through the Composite Architecture
method.
### Environment
- APISIX Ingress controller version (apisix-ingress-controller 1.7.1)
- Kubernetes cluster version (1.20.6) tke
- OS version if running APISIX Ingress controller in a bare-metal
environment (Linux VM-1-200-tlinux 4.14.105-19-0020.1 #1 SMP Fri Apr 23
10:22:59 CST 2021 x86_64 x86_64 x86_64 GNU/Linux) tos
--
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]
