"network-segment-ranges" doesn't return the project_id

Bug #1828205 reported by Rodolfo Alonso on 2019-05-08
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

The client call "GET /v2.0/network-segment-ranges" didn't return the project_id in the response [1]. This behavior was seen only in this test execution. Other tests [2] doesn't reproduce this error.

I'm filling this bug just to track a possible error in the API/Client/SDK.

[1] http://logs.openstack.org/27/642527/4/check/neutron-tempest-plugin-api/9aeecb7/controller/logs/tempest_log.txt.gz#_2019-04-15_12_46_03_016
[2] http://logs.openstack.org/27/642527/4/check/neutron-tempest-plugin-api/99cd8c8/controller/logs/tempest_log.txt.gz#_2019-05-07_22_26_39_882

Changed in neutron:
status: New → Incomplete
Lajos Katona (lajos-katona) wrote :

In a fresh devstack with curl I have no project_id in the response:
$ curl -H "X-Auth-Token: $MY_TOKEN" -X GET |json_pp
   "network_segment_range" : {
      "used" : {
      "default" : true,
      "revision_number" : 0,
      "tags" : [],
      "minimum" : 200,
      "physical_network" : "physnet1",
      "id" : "ade20ea9-c2fe-47c7-805d-591f4e147ddc",
      "created_at" : "2019-05-08T11:56:47Z",
      "shared" : true,
      "network_type" : "vlan",
      "available" : [],
      "name" : "",
      "maximum" : 400

Changed in neutron:
status: Incomplete → Confirmed
importance: Undecided → Medium

Reviewed: https://review.opendev.org/687868
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=70f7b3222a9805ac1c58c25572b2e4e62de4d90a
Submitter: Zuul
Branch: master

commit 70f7b3222a9805ac1c58c25572b2e4e62de4d90a
Author: Rodolfo Alonso Hernandez <email address hidden>
Date: Thu Oct 10 11:48:57 2019 +0000

    Check parameters returned in "list_network_segment_ranges"

    Check that the DB registers returned by listing the network segment
    ranges are the same as in single register retrieval (show vs list).

    Change-Id: I9aee7f2a3108e605c203760a981ac226ecb33ea9
    Related-Bug: #1828205

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers