2019-05-13 17:05:51 |
Rodolfo Alonso |
bug |
|
|
added bug |
2019-05-13 17:07:38 |
OpenStack Infra |
neutron: status |
New |
In Progress |
|
2019-05-13 17:07:38 |
OpenStack Infra |
neutron: assignee |
|
Rodolfo Alonso (rodolfo-alonso-hernandez) |
|
2019-05-14 10:02:16 |
Rodolfo Alonso |
summary |
Force random new IP in "test_port_ip_update_revises" |
Pass the correct subnet to the port creation function in "test_port_ip_update_revises" |
|
2019-05-14 10:04:15 |
Rodolfo Alonso |
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 |
We are hitting sometimes a problem in "test_port_ip_update_revises" [1]. This happens because the port created doesn't belong to the previously created subnet. We need to enforce that the port is created in the subnet specifically created in this test.
[1] http://logs.openstack.org/69/650269/12/check/openstack-tox-lower-constraints/7adf36e/testr_results.html.gz |
|
2019-05-16 23:08:46 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
2019-06-19 14:54:04 |
Bernard Cafarelli |
tags |
|
neutron-proactive-backport-potential |
|
2019-09-09 23:54:54 |
OpenStack Infra |
tags |
neutron-proactive-backport-potential |
in-stable-rocky neutron-proactive-backport-potential |
|
2019-09-09 23:55:04 |
OpenStack Infra |
tags |
in-stable-rocky neutron-proactive-backport-potential |
in-stable-queens in-stable-rocky neutron-proactive-backport-potential |
|
2019-09-11 06:58:30 |
OpenStack Infra |
tags |
in-stable-queens in-stable-rocky neutron-proactive-backport-potential |
in-stable-queens in-stable-rocky in-stable-stein neutron-proactive-backport-potential |
|