github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-30 15:05:27 +00:00
Code Issues Projects Releases Wiki Activity

node not exist during node status update should not block others

Browse Source 
When node is deleted, attach-detach controller cache may contain stale
information of this node, and update node status fails in reconciler
loop. But one node update failure should not block updating other nodes.
Also the warning message easily flush the log file. This PR is just a quick
fix of this issue. More complete fix including make sure controller cache
up to date will be addressed in another PR.
This commit is contained in:
Jing Xu 2016-08-18 10:18:56 -07:00
parent 2166ce2fdc
commit 70deeb0ae4
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
pkg/controller/volume/attachdetach/statusupdater/node_status_updater.go
View File

@ -63,7 +63,7 @@ func (nsu *nodeStatusUpdater) UpdateNodeStatuses() error {
nodeObj, exists, err := nsu.nodeInformer.GetStore().GetByKey(nodeName)
if nodeObj == nil || !exists || err != nil {
// If node does not exist, its status cannot be updated, log error and move on.
glog.Warningf(
glog.V(5).Infof(
"Could not update node status. Failed to find node %q in NodeInformer cache. %v",
nodeName,
err)