-
-
Notifications
You must be signed in to change notification settings - Fork 67
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]: Too old resource version #724
Comments
Hi, I'm facing the same problem. If I leave the operator there without performing any operation for a while(the amount of time needed for the error to appear is random) the same error occurs to me. I tried to study a bit the situation, this is my understanding: When the operator wants to watch a list of resources it has to perform a LIST operation. It will obtain the current status of the asked resources. The resourceVersion obtained is used to start a WATCH (and saved in the "_lastResourceVersion" property of ResourceWatcher class). Every time an event related to the watched resources occurs, the "_lastResourceVersion" property is updated. When the current WATCH operation is too old, a new WATCH must be started: the saved resourceVersion will be used:
Currently this leads to an infinite loop where the same invalid ResourceVersion is continuously used. @buehler am I correct? Thanks for your work. |
@gabrieledemaglie I think you are correct :) |
I'm facing this issue too, any resolution @buehler? |
Fixes #724 Restart the watch loop when we receive HTTP 410 Gone, which seems to mirror what other k8s frameworks are doing (see: java).
Describe the bug
Hi.
After having a operator running for a few days I start getting these errors and the operator stops working.
fail: KubeOps.Operator.Watcher.ResourceWatcher[0]
There was an error while watching the resource "XXX".
k8s.KubernetesException: too old resource version: XXXXXX (XXXXXX)
To reproduce
Watch a custom resource for a few days
Expected behavior
The operator continues to work all the time
Screenshots
No response
Additional Context
Version 8.0.1
The text was updated successfully, but these errors were encountered: