port id should be int in network interface schema

Bug #1630276 reported by Sulochan Acharya
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
craton
Fix Released
High
Sulochan Acharya

Bug Description

port id should be int in network interface schema

https://github.com/openstack/craton/blob/master/craton/api/v1/schemas.py#L199

should be

port: integer

Changed in craton:
importance: Undecided → High
Changed in craton:
assignee: nobody → Sulochan Acharya (sulochan-acharya)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to craton (master)

Reviewed: https://review.openstack.org/439832
Committed: https://git.openstack.org/cgit/openstack/craton/commit/?id=bb4304eeeeb4156c77e6065e31fa95815e38018a
Submitter: Jenkins
Branch: master

commit bb4304eeeeb4156c77e6065e31fa95815e38018a
Author: Ian Cordasco <email address hidden>
Date: Wed Mar 1 14:15:07 2017 -0600

    Update schema definition for network interfaces port

    Previously, listing or creating a network interface required the port be
    an integer. Updating the port, however, allowed it to be a string
    instead of similarly requiring it to be an integer. This updates the
    constraint and adds the basis of functional testing for those endpoints.

    Closes-bug: #1630276
    Change-Id: Ic99d73dfd63fb3fe9a64d41ca2b8eafe4ff1c253

Changed in craton:
status: In Progress → Fix Released
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.