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
Merge pull request #18758 from pravisankar/fix-clear-nodenetwork
Automatic merge from submit-queue.
Bug 1550266 - Fix clearInitialNodeNetworkUnavailableCondition() in sdn master
#This change fixes these 2 issues:
- Currently, clearing NodeNetworkUnavailable node condition only works
if we are successful in updating the node status during the first iteration.
Subsequent retries will not work because:
1. knode != node
2. node.Status is updated in memory
3. UpdateNodeStatus(knode)
(3) will have no effect as in step (2) node.Status is updated but not knode.Status
- Node object passed to this method is pointer to an item in the informer
cache and it should not be modified directly.
Avoid NodeNetworkUnavailable condition check for every node status update
- We know that kubelet sets NodeNetworkUnavailable condition when the node is
created/registered with api server.
- So we only need to call clearInitialNodeNetworkUnavailableCondition()
for the first time and not during subsequent node status update events.
0 commit comments