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/05/06 11:56:01 UTC
[GitHub] [apisix-ingress-controller] Donghui0 opened a new issue #421: bug: The upstream associated with other routes cannot be deleted, and the delete event keeps retrying
Donghui0 opened a new issue #421:
URL: https://github.com/apache/apisix-ingress-controller/issues/421
### Issue description
controller log as below:
upstream delete failed, The delete event is added to the queue again.
### Environment
* apisix-ingress-controller version: v0.5.0
* Kubernetes cluster version: v1.16.9
### Minimal test code / Steps to reproduce the issue
1. create apisix route, service field references an existing k8s service.
2. delete apisix route resouce
### What's the actual result? (including assertion message & call stack if applicable)
the delete event keeps retrying....
### What's the expected result?
ignore related upstream
add resp.StatusCode != 400 condition ?
--
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 #421: bug: The upstream associated with other routes cannot be deleted, and the delete event keeps retrying
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #421:
URL: https://github.com/apache/apisix-ingress-controller/issues/421#issuecomment-834078549
@Donghui0 Thanks for your report, I have captured the root reason about this bug, I will fix it.
--
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 #421: bug: The upstream associated with other routes cannot be deleted, and the delete event keeps retrying
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #421:
URL: https://github.com/apache/apisix-ingress-controller/issues/421#issuecomment-834016422
> We may need to handle the given error from the caching operation.
Ignore this please.
--
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 #421: bug: The upstream associated with other routes cannot be deleted, and the delete event keeps retrying
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #421:
URL: https://github.com/apache/apisix-ingress-controller/issues/421#issuecomment-833569624
We may need to handle the given error from the caching operation.
--
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 #421: bug: The upstream associated with other routes cannot be deleted, and the delete event keeps retrying
Posted by GitBox <gi...@apache.org>.
tokers closed issue #421:
URL: https://github.com/apache/apisix-ingress-controller/issues/421
--
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