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

bug: The upstream associated with other routes cannot be deleted, and the delete event keeps retrying #421

Closed
Donghui0 opened this issue May 6, 2021 · 3 comments · Fixed by #422
Milestone

Comments

@Donghui0
Copy link
Contributor

Donghui0 commented May 6, 2021

Issue description

controller log as below:
image

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

image
add resp.StatusCode != 400 condition ?

@tokers
Copy link
Contributor

tokers commented May 6, 2021

We may need to handle the given error from the caching operation.

@tokers
Copy link
Contributor

tokers commented May 7, 2021

We may need to handle the given error from the caching operation.

Ignore this please.

@tokers
Copy link
Contributor

tokers commented May 7, 2021

@Donghui0 Thanks for your report, I have captured the root reason about this bug, I will fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants