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

Log spam with "Could not update node status." #15757

Closed
andrewklau opened this issue Aug 12, 2017 · 2 comments
Closed

Log spam with "Could not update node status." #15757

andrewklau opened this issue Aug 12, 2017 · 2 comments
Assignees
@derekwaynecarr
Labels
component/kubernetes priority/P2

Comments

@andrewklau
Copy link
Contributor

Since 3.6 if I remove a node I end up with a LOT of log spam:

Aug 13 00:41:51 ip-10-0-1-252.ap-southeast-2.compute.internal origin-master-controllers[128079]: I0812 14:41:51.011811       1 node_status_updater.go:74] Could not update node status. Failed to find node "ip-10-0-123-94.ap-southeast-2.compute.internal" in NodeInformer cache. node "ip-10-0-123-94.ap-southeast-2.compute.internal" not found
Aug 13 00:41:51 ip-10-0-1-252.ap-southeast-2.compute.internal origin-master-controllers[128079]: I0812 14:41:51.011847       1 node_status_updater.go:74] Could not update node status. Failed to find node "ip-10-0-109-119.ap-southeast-2.compute.internal" in NodeInformer cache. node "ip-10-0-109-119.ap-southeast-2.compute.internal" not found
Aug 13 00:41:51 ip-10-0-1-252.ap-southeast-2.compute.internal dockerd-current[2476]: I0812 14:41:51.011811       1 node_status_updater.go:74] Could not update node status. Failed to find node "ip-10-0-123-94.ap-southeast-2.compute.internal" in NodeInformer cache. node "ip-10-0-123-94.ap-southeast-2.compute.internal" not found
Aug 13 00:41:51 ip-10-0-1-252.ap-southeast-2.compute.internal dockerd-current[2476]: I0812 14:41:51.011847       1 node_status_updater.go:74] Could not update node status. Failed to find node "ip-10-0-109-119.ap-southeast-2.compute.internal" in NodeInformer cache. node "ip-10-0-109-119.ap-southeast-2.compute.internal" not found
@andrewklau
Copy link
Contributor Author

Found it kubernetes/kubernetes#42438

@andrewklau
Copy link
Contributor Author

Looks like it's fixed in kubernetes. Will close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@derekwaynecarr derekwaynecarr

Labels
component/kubernetes priority/P2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@andrewklau @pweil- @derekwaynecarr