← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1828205] Re: "network-segment-ranges" doesn't return the project_id

 

Reviewed:  https://review.opendev.org/707898
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3053caaa02adaadfffa53fb1070aaa60f49419e8
Submitter: Zuul
Branch:    master

commit 3053caaa02adaadfffa53fb1070aaa60f49419e8
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Fri Feb 14 18:40:09 2020 +0000

    Workaround in NetworkSegmentRange OVO until "project_id" migration
    
    The "network_segment_range" service plugin API does not have
    "tenant_id" as parameter. However, because the migration from
    "tenant_id" to "project_id" did not finish, every OVO with
    "project_id" will also have "tenant_id" as an extra field. This
    extra field will be populated with the same value as the
    "project_id" field.
    
    If the Neutron API WSGI is used and "tenant_id" is not present in
    the API (defined in neutron-lib), both "tenant_id" and "project_id"
    parameters will be removed from the response.
    
    This patch introduces a workaround for this OVO until the migration
    is over.
    
    More information about this patch can be found in the bug c#4.
    
    Change-Id: I85a02d8b59e8a758826c110e00df84672fa93676
    Closes-Bug: #1828205


** 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.
https://bugs.launchpad.net/bugs/1828205

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

Status in neutron:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1828205/+subscriptions


References