Reviewed: https://review.openstack.org/374870
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=f21e7e33298a359f54e4eb5c7089a6a4f13537ee
Submitter: Jenkins
Branch: master
commit f21e7e33298a359f54e4eb5c7089a6a4f13537ee
Author: Chris Dent <cd...@anticdent.org>
Date: Thu Sep 22 14:40:45 2016 +0000
[placement] Allow both /placement and /placement/ to work
When mounted under a prefix (such as /placement) the service was
only returning the home document at /placement/ not /placement. In
the context of having a prefix, we'd generally like the latter to
work and for '/' to work when there is no prefix. This allows both.
Note that this doesn't make /placement/resource_providers/ work, and
we don't want that.
Change-Id: I0ac92bf9982227d5f4915175182e5230aeb039b4
Closes-Bug: #1626490
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1626490
Title:
placement api root resource is only '/' not '' which can lead to
unexpected 404s
Status in OpenStack Compute (nova):
Fix Released
Bug description:
The placement api handler for root is defined as matching '/'. This
works fine in those situations where the requested URL actually
includes the '/' but in some situations it can be easy to not include
it. If, for example, the API is mounted under a prefix like
'/placement' (as in the default devstack setup) then it is possible to
make a request to http://example.com/placement and get a 404 whereas
http://example.com/placement/ will get the expected microversion
information.
This ought to be easy to fix and was basically an oversight.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1626490/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
