Needless to say, 13.7 ms after I sent this e-mail, I found this bug report:

https://bugs.launchpad.net/mos/+bug/1527581

Humble apologies...

-Ken


On 2016-04-21 23:11, Ken D'Ambrosio wrote:
I'd heard from some users they were having trouble allocating floating
IPs in our Liberty cloud, so I tried on my test account.  I had two
floating IPs (with a quota of (at least) three); I released and
immediately tried to re-acquire, and it failed with:

[Fri Apr 22 02:59:36.839441 2016] [:error] [pid 25146:tid
140282618590976] Recoverable error: Quota exceeded for resources:
['floatingip']

Note that Horizon shows me with one out of my quota of three IPs
allocated and associated.

Helpfully (not), here are the values I get back from various commands:

gbadmin@openstack-cli:~ liberty(prod)$ openstack quota show kentenant
| grep float
| floating-ips          | 50        |

gbadmin@openstack-cli:~ liberty(prod)$ neutron quota-show | grep float
| floatingip            | 50    |

gbadmin@openstack-cli:~ liberty(prod)$ nova quota-show | grep float
| floating_ips                | 10    |

You'll note that none of these is the "three" shown in Horizon.

Regardless, even if they were, I should still have two floating IPs
available to me, as I have exactly one allocated.  Smells like a bug
to me -- perhaps released addresses not being returned to a pool?
Googling hasn't shown me anything of note; any ideas?

Thanks,

-Ken

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Reply via email to