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 protected]> 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 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1696682 Title: port_range validator should allow a single integer Status in neutron: Fix Released 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. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1696682/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
