| 2015-10-19 21:15:59 |
Claudiu Belu |
bug |
|
|
added bug |
| 2015-10-19 21:18:23 |
Claudiu Belu |
description |
neutron-openvswitch-agent seems to create wrong OVS flows for newly created networks. This causes package losses, including lost DHCP requests, resulting in instances that did not receive an IP. This can cause tempest tests to fail.
This issue has been observed in the Liberty release.
Details: http://paste.openstack.org/show/476764/
IRC discussion: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2015-10-19.log.html#t2015-10-19T20:27:31 |
neutron-openvswitch-agent seems to create wrong OVS flows for newly created networks. This causes package losses, including lost DHCP requests, resulting in instances that did not receive an IP. This can cause tempest tests to fail.
Restarting the neutron-openvswitch-agent will result in properly created OVS flows, and the traffic flowing properly.
This issue has been observed in the Liberty release.
Details: http://paste.openstack.org/show/476764/
IRC discussion: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2015-10-19.log.html#t2015-10-19T20:27:31 |
|
| 2015-10-19 21:26:44 |
Claudiu Belu |
description |
neutron-openvswitch-agent seems to create wrong OVS flows for newly created networks. This causes package losses, including lost DHCP requests, resulting in instances that did not receive an IP. This can cause tempest tests to fail.
Restarting the neutron-openvswitch-agent will result in properly created OVS flows, and the traffic flowing properly.
This issue has been observed in the Liberty release.
Details: http://paste.openstack.org/show/476764/
IRC discussion: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2015-10-19.log.html#t2015-10-19T20:27:31 |
neutron-openvswitch-agent seems to create wrong OVS flows for newly created networks. This causes package losses, including lost DHCP requests, resulting in instances that did not receive an IP. This can cause tempest tests to fail.
Restarting the neutron-openvswitch-agent will result in properly created OVS flows, and the traffic flowing properly.
The issue has been observed using VLAN as a network_type, while running tempest tests: tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.
For example, testr run tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops randomly fails due to the fact that the instance did not get any reply for its DHCP request. NOTE: while the OVS flows are wrong for each run of the test, the test still has a small chance of success.
This issue has been observed in the Liberty release.
Details: http://paste.openstack.org/show/476764/
IRC discussion: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2015-10-19.log.html#t2015-10-19T20:27:31 |
|
| 2015-10-19 21:28:12 |
Claudiu Belu |
description |
neutron-openvswitch-agent seems to create wrong OVS flows for newly created networks. This causes package losses, including lost DHCP requests, resulting in instances that did not receive an IP. This can cause tempest tests to fail.
Restarting the neutron-openvswitch-agent will result in properly created OVS flows, and the traffic flowing properly.
The issue has been observed using VLAN as a network_type, while running tempest tests: tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.
For example, testr run tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops randomly fails due to the fact that the instance did not get any reply for its DHCP request. NOTE: while the OVS flows are wrong for each run of the test, the test still has a small chance of success.
This issue has been observed in the Liberty release.
Details: http://paste.openstack.org/show/476764/
IRC discussion: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2015-10-19.log.html#t2015-10-19T20:27:31 |
neutron-openvswitch-agent seems to create wrong OVS flows for newly created networks. This causes package losses, including lost DHCP requests, resulting in instances that did not receive an IP. This can cause tempest tests to fail.
Restarting the neutron-openvswitch-agent will result in properly created OVS flows, and the traffic flowing properly.
The issue has been observed using VLAN as a network_type and no other special configurations (like DVR being enabled), while running tempest tests: tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.
For example, testr run tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops randomly fails due to the fact that the instance did not get any reply for its DHCP request. NOTE: while the OVS flows are wrong for each run of the test, the test still has a small chance of success.
This issue has been observed in the Liberty release.
Details: http://paste.openstack.org/show/476764/
IRC discussion: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2015-10-19.log.html#t2015-10-19T20:27:31 |
|
| 2015-10-19 21:31:46 |
Claudiu Belu |
description |
neutron-openvswitch-agent seems to create wrong OVS flows for newly created networks. This causes package losses, including lost DHCP requests, resulting in instances that did not receive an IP. This can cause tempest tests to fail.
Restarting the neutron-openvswitch-agent will result in properly created OVS flows, and the traffic flowing properly.
The issue has been observed using VLAN as a network_type and no other special configurations (like DVR being enabled), while running tempest tests: tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.
For example, testr run tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops randomly fails due to the fact that the instance did not get any reply for its DHCP request. NOTE: while the OVS flows are wrong for each run of the test, the test still has a small chance of success.
This issue has been observed in the Liberty release.
Details: http://paste.openstack.org/show/476764/
IRC discussion: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2015-10-19.log.html#t2015-10-19T20:27:31 |
neutron-openvswitch-agent seems to create wrong OVS flows for newly created networks. This causes package losses, including lost DHCP requests, resulting in instances that did not receive an IP. This can cause tempest tests to fail.
Restarting the neutron-openvswitch-agent will result in properly created OVS flows, and the traffic flowing properly.
The issue has been observed using VLAN as a network_type and no other special configurations (like DVR being enabled), while running tempest tests: tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.
For example, testr run tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops randomly fails due to the fact that the instance did not get any reply for its DHCP request. NOTE: while the OVS flows are wrong for each run of the test, the test still has a small chance of success.
Hypervisor used: Hyper-V. The port on Hyper-V are properly bound and the VLAN tag properly set, the ports are marked as "alive". The network traffic arrives with the proper VLAN tag at the Networking Controller.
This issue has been observed in the Liberty release.
Details: http://paste.openstack.org/show/476764/
IRC discussion: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2015-10-19.log.html#t2015-10-19T20:27:31 |
|
| 2015-10-19 21:32:15 |
Claudiu Belu |
description |
neutron-openvswitch-agent seems to create wrong OVS flows for newly created networks. This causes package losses, including lost DHCP requests, resulting in instances that did not receive an IP. This can cause tempest tests to fail.
Restarting the neutron-openvswitch-agent will result in properly created OVS flows, and the traffic flowing properly.
The issue has been observed using VLAN as a network_type and no other special configurations (like DVR being enabled), while running tempest tests: tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.
For example, testr run tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops randomly fails due to the fact that the instance did not get any reply for its DHCP request. NOTE: while the OVS flows are wrong for each run of the test, the test still has a small chance of success.
Hypervisor used: Hyper-V. The port on Hyper-V are properly bound and the VLAN tag properly set, the ports are marked as "alive". The network traffic arrives with the proper VLAN tag at the Networking Controller.
This issue has been observed in the Liberty release.
Details: http://paste.openstack.org/show/476764/
IRC discussion: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2015-10-19.log.html#t2015-10-19T20:27:31 |
neutron-openvswitch-agent seems to create wrong OVS flows for newly created networks. This causes package losses, including lost DHCP requests, resulting in instances that did not receive an IP. This can cause tempest tests to fail.
Restarting the neutron-openvswitch-agent will result in properly created OVS flows, and the traffic flowing properly.
The issue has been observed using VLAN as a network_type and no other special configurations (like DVR being enabled), while running tempest tests: tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.
For example, testr run tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops randomly fails due to the fact that the instance did not get any reply for its DHCP request. NOTE: while the OVS flows are wrong for each run of the test, the test still has a small chance of success.
Hypervisor used: Hyper-V. The port on Hyper-V are properly bound and the VLAN tag properly set, the ports are marked as "alive". The network traffic arrives with the proper VLAN tag at the Networking Controller. The bug is unrelated to neutron-hyperv-agent and Hyper-V.
This issue has been observed in the Liberty release.
Details: http://paste.openstack.org/show/476764/
IRC discussion: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2015-10-19.log.html#t2015-10-19T20:27:31 |
|
| 2015-10-21 05:13:50 |
OpenStack Infra |
neutron: status |
New |
In Progress |
|
| 2015-10-21 05:13:50 |
OpenStack Infra |
neutron: assignee |
|
YAMAMOTO Takashi (yamamoto) |
|
| 2015-10-21 23:56:04 |
Armando Migliaccio |
neutron: importance |
Undecided |
High |
|
| 2015-10-23 15:45:16 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Committed |
|
| 2015-11-02 03:52:33 |
OpenStack Infra |
tags |
liberty-backport-potential ovs |
in-stable-liberty liberty-backport-potential ovs |
|
| 2015-11-13 14:05:34 |
Ihar Hrachyshka |
tags |
in-stable-liberty liberty-backport-potential ovs |
in-stable-liberty ovs |
|
| 2015-12-03 21:01:49 |
Doug Hellmann |
neutron: status |
Fix Committed |
Fix Released |
|
