On 11/18/2014 5:27 PM, Vishvananda Ishaya wrote:
It looks like this has not been reported so a bug would be great. It
looks like it might be as easy as adding the NoMoreFixedIps exception to
the list where FixedIpLimitExceeded is caught in nova/network/manager.py

Vish

On Nov 18, 2014, at 8:13 AM, Edgar Magana <edgar.mag...@workday.com
<mailto:edgar.mag...@workday.com>> wrote:

Hello Community,

When a network subnet runs out of IP addresses a request to create a
VM on that network fails with the Error message: "No valid host was
found. There are not enough hosts available."
In the nova logs the error message is: NoMoreFixedIps: No fixed IP
addresses available for network:

Obviously, this is not the desirable behavior, is there any work in
progress to change it or I should open a bug to properly propagate the
right error message.

Thanks,

Edgar
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Except this is neutron right? In that case nova.network.neutronv2.api needs to translate the NeutronClientException to a NovaException and raise that back up so the compute manager can tell the scheduler it blew up in setting up networking.

When you open a bug, please provide a stacktrace so we know where you're hitting this in the neutronv2 API.

--

Thanks,

Matt Riedemann


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to