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.

Sign up for GitHub

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

Jump to bottom

Sensor-controller throws errors about wrong config map version #81

Closed
shrinandj opened this issue Aug 6, 2018 · 6 comments
Closed

Sensor-controller throws errors about wrong config map version #81

shrinandj opened this issue Aug 6, 2018 · 6 comments

Comments

@shrinandj
Copy link
Contributor

Describe the bug
I keep seeing the sensor-controller spewing log messages about old config map version even though there were no changes made to the config-map.

To Reproduce
Steps to reproduce the behavior:

  1. Run the sensor-controller.
  2. The sensor-controller pod logs the following messages:
ERROR: logging before flag.Parse: W0806 16:24:00.173164       1 reflector.go:341] github.com/argoproj/argo-events/controller/config.go:62: watch of *v1.ConfigMap ended with: too old resource version: 608242 (608445)
time="2018-08-06T16:24:01Z" level=info msg="detected ConfigMap update. updating the controller config."
ERROR: logging before flag.Parse: W0806 16:36:04.188869       1 reflector.go:341] github.com/argoproj/argo-events/controller/config.go:62: watch of *v1.ConfigMap ended with: too old resource version: 609334 (609828)
time="2018-08-06T16:36:05Z" level=info msg="detected ConfigMap update. updating the controller config."
ERROR: logging before flag.Parse: W0806 16:45:17.198521       1 reflector.go:341] github.com/argoproj/argo-events/controller/config.go:62: watch of *v1.ConfigMap ended with: too old resource version: 610721 (610887)
time="2018-08-06T16:45:18Z" level=info msg="detected ConfigMap update. updating the controller config."
ERROR: logging before flag.Parse: W0806 16:54:28.208333       1 reflector.go:341] github.com/argoproj/argo-events/controller/config.go:62: watch of *v1.ConfigMap ended with: too old resource version: 611778 (611949)
time="2018-08-06T16:54:29Z" level=info msg="detected ConfigMap update. updating the controller config."
ERROR: logging before flag.Parse: W0806 17:06:17.222437       1 reflector.go:341] github.com/argoproj/argo-events/controller/config.go:62: watch of *v1.ConfigMap ended with: too old resource version: 612832 (613300)
time="2018-08-06T17:06:18Z" level=info msg="detected ConfigMap update. updating the controller config."
ERROR: logging before flag.Parse: W0806 17:14:14.231619       1 reflector.go:341] github.com/argoproj/argo-events/controller/config.go:62: watch of *v1.ConfigMap ended with: too old resource version: 614188 (614209)
time="2018-08-06T17:14:15Z" level=info msg="detected ConfigMap update. updating the controller config."

Expected behavior
There should be no such errors in the logs
@magaldima
Copy link
Contributor

I see these errors as well on a Kubernetes 1.9 cluster. What version is your cluster?

@shrinandj
Copy link
Contributor Author

v1.10.3

@magaldima
Copy link
Contributor

magaldima commented Aug 7, 2018 •
edited
Loading

Others have encountered this issue long before. I'm not sure if this means the same in this version of Kubernetes/client-go.

Looks like it comes about from etcd <--> apiserver and then apiserver <--> client.

See related issues:

@magaldima
Copy link
Contributor

Looks like this may be due to "slow moving resources" from kubernetes/kubernetes#55230:

getting a "version too old" error and having to start over listing and watching again is normal for watches of slow-moving resources. that's an expected usage pattern

not sure much we can do on this for now besides ignoring these statements, but let's stay up-to-date on any developments here.

@magaldima
Copy link
Contributor

@VaibhavPage can we revisit this? Do you think this was addressed in k/k?

@VaibhavPage
Copy link
Contributor

closing this issue as there is nothing we can do here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@VaibhavPage @shrinandj @magaldima