This repository has been archived by the owner on Oct 22, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 43
IPAM failures when running kubernetes scale test #66
Labels
Comments
@caseydavenport Do you happen to know what version of libcalico this would have been using? |
Hm. @tomdee was using a master build of our kubernetes plugin, which I believe should pull in whatever is used in the latest |
This is a new bug. #47, which is similar, occurred during a |
@spikecurtis Are you expecting to work on this in the next few days? Otherwise I'll take it off your hands? |
@tomdee I haven't started on this because I was worried it would interfere with @robbrockbank's other changes in this area. Happy to have you take it |
tomdee
added a commit
to tomdee/libcalico
that referenced
this issue
Jan 5, 2016
Allow cleanup code in _claim_block_affinity to "fail" if it's safe to do so. Fixes projectcalico#66
tomdee
added a commit
to tomdee/libcalico
that referenced
this issue
Jan 5, 2016
Allow cleanup code in _claim_block_affinity to "fail" if it's safe to do so. Fixes projectcalico#66
Merged
tomdee
added a commit
to tomdee/libcalico
that referenced
this issue
Jan 5, 2016
Allow cleanup code in _claim_block_affinity to "fail" if it's safe to do so. Fixes projectcalico#66
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm not sure if this is a libcalico issue or a kubernetes plugin issue.
When spinning up pods on 25 hosts, I hit this issue on two of the hosts. It caused one pod to fail on the problem hosts. The other hosts had no problems.
The text was updated successfully, but these errors were encountered: