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

failed to allocate for range 0: no IP addresses available in range set #59

Open
debianmaster opened this issue May 2, 2018 · 5 comments

Comments

@debianmaster
Copy link
Owner

Failed create pod sandbox: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "test-hunt-microservice-3-rpdqh_test-test" network: CNI request failed with status 400: 'failed to run IPAM for 065credacted96redacted31ce42c91878: failed to run CNI IPAM ADD: failed to allocate for range 0: no IP addresses available in range set: 10.128.0.1-10.128.1.254 '
111
@debianmaster
Copy link
Owner Author

possible reasons

  1. node running out of ipaddress
  2. cleanup of ips for dead pods is not properly done. (may be bug in older ocp versions)

debugging

check for timestamps here
ls -l /var/lib/cni/networks/openshift-sdn/

Drain the node:

  oc adm drain $node
  systemctl stop atomic-openshift-node
  rm -rf /var/lib/cni/networks/openshift-sdn/*
  systemctl start atomic-openshift-node
  oc adm uncordon $node

@tobiasdenzler
Copy link

Also check cloudnativelabs/kube-router#383. There is a (automatic) workaround using https://github.com/jsenon/api-cni-cleanup.

@debianmaster
Copy link
Owner Author

thanks @tobiasdenzler

@Dorsosiv
Copy link

Is there a built-in solution for this issue in Openshift 4 ? I have this issue in Openshift 4.7.

@debianmaster
Copy link
Owner Author

@donnydavis no clue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants