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

can't update node condition #108

Closed
WIZARD-CXY opened this issue Apr 18, 2017 · 2 comments
Closed

can't update node condition #108

WIZARD-CXY opened this issue Apr 18, 2017 · 2 comments

Comments

@WIZARD-CXY
Copy link

WIZARD-CXY commented Apr 18, 2017

Hi, I deployed npd yesterday in my k8s 1.6, Now I find it can't update node condition.Below is its log

E0418 09:48:32.826374       7 manager.go:160] failed to update node conditions: Operation cannot be fulfilled on nodes "cs55": there is a meaningful conflict (firstResourceVersion: "881081", currentResourceVersion: "881106"):
 diff1={"metadata":{"resourceVersion":"881106"},"status":{"conditions":[{"lastHeartbeatTime":"2017-04-18T01:48:32Z","type":"DiskPressure"},{"lastHeartbeatTime":"2017-04-18T01:47:32Z","type":"KernelDeadlock"},{"lastHeartbeatTime":"2017-04-18T01:48:32Z","type":"MemoryPressure"},{"lastHeartbeatTime":"2017-04-18T01:48:32Z","type":"OutOfDisk"},{"lastHeartbeatTime":"2017-04-18T01:48:32Z","type":"Ready"}]}}
, diff2={"status":{"conditions":[{"lastHeartbeatTime":"2017-04-18T01:48:32Z","lastTransitionTime":"2017-04-17T09:10:43Z","message":"kernel has no deadlock","reason":"KernelHasNoDeadlock","status":"False","type":"KernelDeadlock"}]}}

I wonder why this happen? @Random-Liu thx

@Random-Liu
Copy link
Member

Random-Liu commented Apr 18, 2017

@WIZARD-CXY Do you constantly see this error or only several times?

This error is normal. In a Kubernetes cluster, there are several components updating the same node object, kubelet, node problem detector, node controller etc.

Conflict may happen because of the unavoidable race. However, this should be rare and NPD will retry after the conflict. If you only see this several times, it should be fine.

@WIZARD-CXY
Copy link
Author

got it thx

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

No branches or pull requests

2 participants