[Openstack] used floating_ip counter not decreasing even after removing instance
Brad_Pokorny at symantec.com
Mon Oct 13 16:05:38 UTC 2014
I'm not sure on question 1, but the behavior you're seeing for question 2 is due to "nova quota-update" expecting the tenant ID and not the tenant name.
$ nova help quota-update
usage: nova quota-update [--user <user-id>] [--instances <instances>]
[--cores <cores>] [--ram <ram>]
Update the quotas for a tenant/user.
<tenant-id> ID of tenant to set the quotas for.
So if you specify "nova quota-update --floating_ip 12 [ID of tenant1]", it should work as you expect it.
From: mad Engineer <themadengin33r at gmail.com<mailto:themadengin33r at gmail.com>>
Date: Sunday, October 12, 2014 at 7:58 AM
To: "openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>" <openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>>
Subject: [Openstack] used floating_ip counter not decreasing even after removing instance
in my setup i have created 10 instances each with floating_ip and deleted all instances,with out disassociating floating ip.
Now when i try to associate floating ip with new instance,it shows "unable to associate floating ip" and in dashboard used floating_ip is 10/10 even with only 5 instance and 5 floating_ip actually being used.
i just increased quota to make it work now,but there also encountered few issues:
nova quota-update --floating_ip 12 tenant1
it successfully updated the count to 12 (as per nova quota-show tenant1 but on dashboard value remained the same).
until i used
nova-manage project quota
to fix this:
1.How can i make floating ip quota to decrement when one instance is deleted (with floating ip still associated in it )
2.how to Update quota so that its reflected in dashboard (nova quota-update ,successfully updated the variable but still dashboard was showing old value until used nova-manage project quota)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openstack