You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"}]}}
@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.
Hi, I deployed npd yesterday in my k8s 1.6, Now I find it can't update node condition.Below is its log
I wonder why this happen? @Random-Liu thx
The text was updated successfully, but these errors were encountered: