Public bug reported: We are hitting sometimes a problem in "test_port_ip_update_revises" [1], when the IP is concurrently allocated and used in other port. To prevent that, we can force "_find_ip_address" to return not the first IP but a random one. This will reduce this occurrence.
[1] http://logs.openstack.org/69/650269/12/check/openstack-tox-lower- constraints/7adf36e/testr_results.html.gz ** Affects: neutron Importance: Undecided Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1828865 Title: Force random new IP in "test_port_ip_update_revises" Status in neutron: In Progress Bug description: We are hitting sometimes a problem in "test_port_ip_update_revises" [1], when the IP is concurrently allocated and used in other port. To prevent that, we can force "_find_ip_address" to return not the first IP but a random one. This will reduce this occurrence. [1] http://logs.openstack.org/69/650269/12/check/openstack-tox-lower- constraints/7adf36e/testr_results.html.gz To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1828865/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
