port_range validator should allow a single integer

Bug #1696682 reported by YAMAMOTO Takashi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Critical
YAMAMOTO Takashi

Bug Description

neutron-lib version of the validator assumes it's a string.
but it used to accept an integer. for compatibility it should accept an integer.

tags: added: midokura-jira-tracked
Changed in neutron:
assignee: nobody → YAMAMOTO Takashi (yamamoto)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron-lib (master)

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

Changed in neutron:
importance: Undecided → Critical
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron-lib (master)

Reviewed: https://review.openstack.org/472155
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=29a31c152caacdb4d73acb534260443fd07801b0
Submitter: Jenkins
Branch: master

commit 29a31c152caacdb4d73acb534260443fd07801b0
Author: YAMAMOTO Takashi <email address hidden>
Date: Thu Jun 8 17:39:58 2017 +0900

    Make port_range validator accept an integer

    It used to accept an integer but it has been changed for
    some reasons when migrating to neutron-lib.
    For compatibility, it's better to keep the original behaviour.
    After all, the original behaviour seems reasonable to me.

    Closes-Bug: #1696682
    Related-Bug: #1696389
    Change-Id: I60e1a99780202de14522f592288d3a9af7a75592

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

This issue was fixed in the openstack/neutron-lib 1.8.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.