Created attachment 1094840 [details] Part of Neutron server log Description of problem: When running tox -eall tempest.api.network.test_ports while IPAM reference driver is enabled (i.e. ipam_driver = internal in /etc/neutron/neutron.conf) the tests fail. In the Neutron server log: "UPDATE statement on table 'ipamavailabilityranges' expected to update 1 row(s); 0 were matched." Part of the Neutron Log server is attached. Version-Release number of selected component (if applicable): openstack-neutron-7.0.1-dev28.el7.centos.noarch openstack-neutron-common-7.0.1-dev28.el7.centos.noarch python-neutron-7.0.1-dev28.el7.centos.noarch openstack-neutron-ml2-7.0.1-dev28.el7.centos.noarch openstack-neutron-openvswitch-7.0.1-dev28.el7.centos.noarch How reproducible: Steps to Reproduce: 1. Enable IPAM reference driver ipam_driver = internal in /etc/neutron/neutron.conf 2. Restart neutron server 3. Run tox -eall tempest.api.network.test_ports Actual results: Tests fail Expected results: Additional info:
What test failed? Does it fail consistently if you run that test alone? Does it fail only if you run it with other tests? Which tests? What is the minimum set of tests that fails? Does it fail consistently or not? From the u/s bug you linked, it looks like the solution is: https://review.openstack.org/#/c/223123/ It's a pretty invasive change, so we need to measure cost-benefit of backporting it. We need answers to the questions above, then analyze the failing test and understand if it's an issue that is likely to be hit in production, or is it an issue only hit during synthetic testing conditions.
Hi, It's not consistent. The following test fails consistently tough: tempest.api.network.test_ports.PortsTestJSON.test_update_port_with_two_security_groups_and_extra_attributes
I tried backporting the patch in the launchpad bug you linked to this RHBZ: https://review.openstack.org/#/c/284438/. The patch is WIP and it enables pluggable IPAM by default, to see how it fairs at the gate. Let's wait and see. That being said, looking at https://review.openstack.org/#/c/181023, it looks like Tempest is not passing with pluggable IPAM on master either.
Short update - From the u/s backport, one of the feature authors said that a cause of some of the failures is due to bug https://bugs.launchpad.net/neutron/+bug/1543094, and that he'll be working on it shortly.
https://review.openstack.org/#/c/292207/ was fixed to upstream stable/mitaka, once it hits RDO stable/mitaka, we should test if Tempest is reliable with pluggable IPAM.
This is very stale, closing.