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

Instance is Not Removed from IG when node is marked as unschedulable #591

Closed
freehan opened this issue Dec 20, 2018 · 2 comments
Closed
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@freehan
Copy link
Contributor

freehan commented Dec 20, 2018

How to reproduce it (as minimally and precisely as possible):

kubectl cordon ${Node}

What happened:

Ingress controller did not remove the corresponding instance from IG and emit error messages like this:

E1220 14:43:16.052232  257911 instances.go:214] Failed to get zones for e2e-test-mixia-minion-group-3mzg: node not found e2e-test-mixia-minion-group-3mzg, skipping

What you expected to happen:
Unschedulable node got removed from instance group.

Root Cause:
Ingress controller failed to look up the corresponding zone of the instance when the node is marked as unschedulable. This is because the util function GetZoneForNode filter out the nodes that are not ready OR unschedulable. This is introduced here: #370

I think the GetZoneForNode should not filter out any nodes. It should return the zone of the node whenever is necessary. Thoughts?

/kind bug

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Dec 20, 2018
@freehan freehan self-assigned this Dec 20, 2018
@MrHohn
Copy link
Member

MrHohn commented Dec 20, 2018

#576 is attempting to remove the predicate filter.

@freehan
Copy link
Contributor Author

freehan commented Jan 2, 2019

closing this as #576 is merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants