List ports fails due to dummy pod entry

Bug #1652588 reported by Zhiyuan Cai
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Tricircle
Fix Released
Undecided
Zhiyuan Cai

Bug Description

How to reproduce:

Add a dummy pod entry via pod API:

curl -X POST http://127.0.0.1:19999/v1.0/pods -H "Content-Type: application/json" -H "X-Auth-Token: $token" -d '{"pod": {"pod_name": "RegionTwo", "az_name": "az2"}}'

where "RegionTwo" is not a valid Keystone region with no endpoints registered.

Then issue port list request to central Neutron server, get InternalServerError, the log shows

"EndpointNotFound: Endpoint for neutron in c1d68184-1498-4576-a802-b1e01e37adda not found"

Changed in tricircle:
assignee: nobody → Zhiyuan Cai (luckyvega-g)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tricircle (master)

Fix proposed to branch: master
Review: https://review.openstack.org/414898

Changed in tricircle:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tricircle (master)

Reviewed: https://review.openstack.org/414898
Committed: https://git.openstack.org/cgit/openstack/tricircle/commit/?id=2ceebb04e6c6e3d97bd019112c104fc8abbbb564
Submitter: Jenkins
Branch: master

commit 2ceebb04e6c6e3d97bd019112c104fc8abbbb564
Author: zhiyuan_cai <email address hidden>
Date: Mon Dec 26 16:25:19 2016 +0800

    Fix list port failure due to dummy pod entry

    1. What is the problem?
    If a dummy pod whose region doesn't register any endpoints in Keystone
    is created via pod API, port list request to central Neutron server will
    fail with EndpointNotFound error.

    2. What is the solution to the problem?
    Instead of raising EndpointNotFound error, client returns default value
    (None or empty list).

    3. What the features need to be implemented to the Tricircle
       to realize the solution?
    Handle functions in client module return default value when endpoint
    url for given service and pod is not found in Keystone.

    Change-Id: I3b3667c08cf7a57de35bb49548f41742aeb5e25b
    Closes-Bug: #1652588

Changed in tricircle:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tricircle 3.0.0

This issue was fixed in the openstack/tricircle 3.0.0 release.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.