Submitter: Jenkins
Branch:    master

commit 1d01864c066155939e84b0402730f1266b091841
Author: Sergey Belous <>
Date:   Mon Oct 10 17:20:42 2016 +0300

    Added trailing slash in link to Networking API v2.0
    Closes-bug: #1631466
    Change-Id: I310ea62f210ec2d4250d0f93c3081356f429fc41

** Changed in: neutron
       Status: In Progress => Fix Released

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.

  GEt on /v2.0 fails with a 404

Status in neutron:
  Fix Released

Bug description:
  Following the networking API reference to list versions of the network
  API, I can list versions from the network endpoint like this:

  And get details on each version like this:

  However, in practice, using master neutron:

  stack@osc:/opt/stack/neutron$ git log -1
  commit 80d4df144d62ce638ca7bdd228cdd116e34b3067
  Merge: 3ade301 fc93f7f
  Author: Jenkins <>
  Date:   Wed Oct 5 15:36:06 2016 +0000

      Merge "Relocate Flavor and ServiceProfile DB models"

  The 2nd route to get v2.0 details fails:

  stack@osc:~$ curl -g -H "X-Auth-Token: $OS_TOKEN" | 
    % Total    % Received % Xferd  Average Speed   Time    Time     Time  
                                   Dload  Upload   Total   Spent    Left  Speed
  100   118  100   118    0     0  33541      0 --:--:-- --:--:-- --:--:-- 39333
     "versions" : [
           "id" : "v2.0",
           "links" : [
                 "rel" : "self",
                 "href" : "";
           "status" : "CURRENT"

  stack@osc:~$ curl -g -H "X-Auth-Token: $OS_TOKEN"
  404 Not Found

  The resource could not be found.


  So either the docs are wrong, or the API is busted.

  It looks like this is what should handle the /v2.0 route though:

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to