flavor data ignored by router tests

[Manjeet Singh Bhatia]

as neutron/tests/unit/extensions/test_l3.py is used networking-odl for functional tests, it ignores flavor data because flavor_id is not included in hardcoded argument list.

suppose using aforementioned framework some try to create test routers

with self.router(flavor_id=flavor_id) as router:
   some code

it will discard the flavor, request will either fallback to driver in neutron or emits error response
saying Flavor None not found.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/566736
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0dc8e7fbfb368d208e1278a2357b31a3e0a0a595
Submitter: Zuul
Branch: master

commit 0dc8e7fbfb368d208e1278a2357b31a3e0a0a595
Author: Manjeet Singh Bhatia <email address hidden>
Date: Mon May 7 21:00:01 2018 +0000

    Add flavor_id argument to router tests.

    As neutron/tests/unit/extensions/test_l3.py is used networking-odl for
    functional tests, it ignores flavor data because flavor_id is not
    included in hardcoded argument list.

    Change-Id: I1826f50233dcf83f991e78d59ce1d3df2bc9013b
    Closes-Bug: #1769751

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 13.0.0.0b3 development milestone.