Comment 16 for bug 973442

I am also experiencing this issue in Folsom, even though the patch appears to be part of the code already.

I am running a multinode installation with nova-network instances on all the nodes. While booting an instance on a compute-only node I get an error

    {u'message': u'NoValidHost', u'code': 500, u'created': u'2012-12-19T22:24:25Z'}

And the nova-network.log on the node in question shows

     2012-12-19 23:26:39 ERROR nova.network.manager [req-445d7128-60e7-4b9e-899b-a5eab4f4c297 41f0850b0dfe487cad02c13c8ea45dda 908a8e207bd047a49bc0717f7a4a2477] Unable to release 192.168.100.9 because vif doesn't exist.

Is it maybe relevant that I only created the VM IP pool on the controller node?

An interesting thing is that everything worked while I only had 2 nodes (controller + compute) and this error started appearing after I added a 3rd node (compute) - and only on the two compute nodes.

     sudo nova-manage network create private --multi_host=T --fixed_range_v4=192.168.100.0/24 --bridge_interface=br100 --num_networks=1 --network_size=256