Bug 1329502

Summary: Inconsistency quota size nova, neutron, openstack command
Product: Red Hat OpenStack Reporter: Shinobu KINJO <skinjo>
Component: python-novaclientAssignee: Diana Clarke <dclarke>
Status: CLOSED WONTFIX QA Contact: nlevinki <nlevinki>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0 (Kilo)CC: berrange, dasmith, dclarke, eglynn, jruzicka, kchamart, sbauza, sferdjao, sgordon, srevivo, vromanso
Target Milestone: asyncKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-13 14:32:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Shinobu KINJO 2016-04-22 06:26:22 UTC 
[DESCRIPTION]

`neutron quota-show --os-user-name admin` shows:

[root@localhost ~(keystone_admin)]# neutron quota-show --os-user-name admin | grep float
| floatingip          | 50    |

and

`openstack quota show admin` shows:

[root@localhost ~(keystone_admin)]# openstack quota show admin | grep float
| floating-ips         | 50    |

but

`nova --os-user-name admin quota-show` shows:

[root@localhost ~(keystone_admin)]# nova --os-user-name admin quota-show | grep float
| floating_ips                | 10    |

Ouch!

[PACKAGE VERSION]
openstack-nova-common-2015.1.3-7.el7ost.noarch
python-novaclient-2.23.0-2.el7ost.noarch
openstack-nova-compute-2015.1.3-7.el7ost.noarch
openstack-nova-novncproxy-2015.1.3-7.el7ost.noarch
openstack-nova-cert-2015.1.3-7.el7ost.noarch
python-nova-2015.1.3-7.el7ost.noarch
openstack-nova-conductor-2015.1.3-7.el7ost.noarch
openstack-nova-console-2015.1.3-7.el7ost.noarch
openstack-nova-api-2015.1.3-7.el7ost.noarch
openstack-nova-scheduler-2015.1.3-7.el7ost.noarch
Comment 2 Diana Clarke 2016-05-13 14:32:14 UTC 
This is a known issue when you use neutron rather than nova-network. That is, you shouldn't use the nova client (`nova quota-show`) for networking things (like floating ips) if you're using the neutron.

The workaround is to use the openstack client (`openstack quota show`), or the neutron client (`neutron quota-show`) instead.

I will look into making the documentation clearer for this case because it doesn't look like this is going to be fixed upstream, and it's clearly confusing.

There's been a lot of discussion upstream on this front, here's a slice of it:

Bug #1263628 - nova floatingip quota conflicts with neutron floating ip quota
https://bugs.launchpad.net/nova/+bug/1263628

Bug #1186354 - Limits API doesn't work with Neutron
https://bugs.launchpad.net/nova/+bug/1186354

Spec (status: -1 in Mitaka) - Get quota and usage from neutron for limit APIs spec
https://review.openstack.org/#/c/206735/

Mailing list thread - proxy quota/limits info from neutron
http://lists.openstack.org/pipermail/openstack-dev/2015-July/069513.html