Reviewed: https://review.openstack.org/354951 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=aa52367f78be0941ab7a75ade29a30cd853bbbec Submitter: Jenkins Branch: master
commit aa52367f78be0941ab7a75ade29a30cd853bbbec Author: Shih-Hao Li <[email protected]> Date: Fri Aug 12 11:59:38 2016 -0700 Fix test_router_add_interface_delete_port_after_failure In test_router_add_interface_delete_port_after_failure, when a subnet is created, a neutron DHCP port could be created if this subnet is DHCP-enabled. In this case, the test will fail because it only checks if a router-interface port is deleted and expects no more port in the system. But it misses the internal DHCP port is still there. The patch here is to explicitly set enable_dhcp=False when creating the subnet. Change-Id: I4acbf2c83f9145f7b99519ec90934fa862de67f7 Closes-Bug: #1612894 ** 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/1612894 Title: test_router_add_interface_delete_port_after_failure may fail due to extra port created Status in neutron: Fix Released Bug description: In test_router_add_interface_delete_port_after_failure, when a subnet is created, a neutron DHCP port could be created if this subnet is DHCP-enabled. In this case, the test will fail because it only checks if a router-interface port is deleted and expects no more port in the system. But it misses the internal DHCP port is still there. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1612894/+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
