yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #22299
[Bug 1373337] [NEW] Updating quotas path issue
Public bug reported:
In the docs (http://developer.openstack.org/api-ref-networking-v2.html
#quotas-ext), it clearly says that to update quota values, the request
should be:
PUT /v2.0/quotas
But I'm getting a 404 when you do this. If you do this instead:
PUT /v2.0/quotas/foo
it works as expected, where "foo" can literally be anything. I looked at
how the python-neutronclient handles this, and they seem to append the
tenant_id to the end - which is completely undocumented. So:
1. Is this a bug with the Neutron API or with the Neutron docs?
2. Why does any arbitrary string get accepted?
I'm using Neutron on devstack, Icehouse release.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1373337
Title:
Updating quotas path issue
Status in OpenStack Neutron (virtual network service):
New
Bug description:
In the docs (http://developer.openstack.org/api-ref-networking-v2.html
#quotas-ext), it clearly says that to update quota values, the request
should be:
PUT /v2.0/quotas
But I'm getting a 404 when you do this. If you do this instead:
PUT /v2.0/quotas/foo
it works as expected, where "foo" can literally be anything. I looked
at how the python-neutronclient handles this, and they seem to append
the tenant_id to the end - which is completely undocumented. So:
1. Is this a bug with the Neutron API or with the Neutron docs?
2. Why does any arbitrary string get accepted?
I'm using Neutron on devstack, Icehouse release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1373337/+subscriptions
Follow ups
References