Skip to content
This repository has been archived by the owner on Feb 8, 2021. It is now read-only.

failed to allocate IP: no available ip available on network #637

Open
minzcmu opened this issue Dec 4, 2017 · 0 comments
Open

failed to allocate IP: no available ip available on network #637

minzcmu opened this issue Dec 4, 2017 · 0 comments
Assignees

Comments

@minzcmu
Copy link

minzcmu commented Dec 4, 2017

Hyperd failed to start VMs and got error after running for a while:
failed to allocate IP: no available ip available on network

It's failing at:
https://github.com/hyperhq/hyperd/blob/eef65569d2636b831600392d3c28827d4a831566/daemon/pod/networks.go#L45

return nil, ErrNoAvailableIPs

Suspect that the ips are not released properly cuz there are tons of ips available on host:
https://github.com/hyperhq/hyperd/blob/eef65569d2636b831600392d3c28827d4a831566/daemon/pod/networks.go#L84

More from the log:

]: E1205 00:21:01.751236   12700 json.go:458] SB[vm-iKkbpdOKaD] tty socket closed, quit the reading goroutine: read unix @->/var/run/hyper/vm-iKkbpdOKaD/tty.sock: use of closed network connection
Dec 05 00:21:02 hyperd[12700]: E1205 00:21:02.076548   12700 container.go:1139] Pod[builder-14984] Con[b39c1aae7681(14984)] failed to umount root volume: exit status 1
Dec 05 00:21:02 hyperd[12700]: E1205 00:21:02.076581   12700 decommission.go:588] Pod[builder-14984] Con[b39c1aae7681(14984)] exit status 1
Dec 05 00 hyperd[12700]: E1205 00:21:02.076941   12700 decommission.go:551] Pod[builder-14984] pod stopping failed, failed to decommit the resources: exit status 1

After I restart hyperd, it works fine and doesn't give that err. Can someone help me debug this?

@laijs laijs self-assigned this Dec 5, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants