Fixed issue when attempting to add an internal subnet to a router. 41/58041/1
authorspisarski <s.pisarski@cablelabs.com>
Tue, 29 May 2018 16:53:55 +0000 (10:53 -0600)
committerspisarski <s.pisarski@cablelabs.com>
Tue, 29 May 2018 16:53:55 +0000 (10:53 -0600)
commitf17b5d4631682b4807dc1c4267da65258413ef73
treefa4f5b2ae8b3ed3e5005467992bd7584783a3355
parent5a81c2abb920cfe5ea975c37b390838d586a98b1
Fixed issue when attempting to add an internal subnet to a router.

Internal subnets that are owned by the same user who is creating a
router now can be added properly. Attempted to fix an issue with the
change in https://gerrit.opnfv.org/gerrit/#/c/57853/ that was allowing
for subnets with the same name to be assigned but ended up breaking
this functionality completely.

JIRA: SNAPS-312

Change-Id: I1687f66db47520e93e401d3e9fb5f0c4f45d460f
Signed-off-by: spisarski <s.pisarski@cablelabs.com>
docs/how-to-use/IntegrationTests.rst
snaps/openstack/create_router.py
snaps/openstack/tests/create_router_tests.py
snaps/openstack/utils/neutron_utils.py