[Yahoo-eng-team] [Bug 1460164] Re: restart of openvswitch-switch causes instance network down when l2population enabled

Marking Juno as "Won't fix" for the Ubuntu Cloud Archive since it is EOL. ** Changed in: cloud-archive/juno Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron.

[Yahoo-eng-team] [Bug 1460164] Re: restart of openvswitch-switch causes instance network down when l2population enabled

** Also affects: neutron/kilo Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1460164 Title: restart of openvswitch-switch causes instance

[Yahoo-eng-team] [Bug 1460164] Re: restart of openvswitch-switch causes instance network down when l2population enabled

** Changed in: cloud-archive Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1460164 Title: restart of openvswitch-switch causes instance network

[Yahoo-eng-team] [Bug 1460164] Re: restart of openvswitch-switch causes instance network down when l2population enabled

This bug was fixed in the package neutron - 1:2015.1.3-0ubuntu1 --- neutron (1:2015.1.3-0ubuntu1) trusty-kilo; urgency=medium . [ Corey Bryant ] * d/tests/neutron-agents: Give daemon 5 seconds to start to prevent race. . [ James Page ] * New upstream stable release (LP:

[Yahoo-eng-team] [Bug 1460164] Re: restart of openvswitch-switch causes instance network down when l2population enabled

** Changed in: cloud-archive/icehouse Status: Fix Committed => 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/1460164 Title: restart of openvswitch-switch causes

[Yahoo-eng-team] [Bug 1460164] Re: restart of openvswitch-switch causes instance network down when l2population enabled

This bug was fixed in the package neutron - 1:2014.1.5-0ubuntu3 --- neutron (1:2014.1.5-0ubuntu3) trusty; urgency=medium [ Corey Bryant ] * d/p/make_del_fdb_flow_idempotent.patch: Cherry pick from Juno to prevent KeyError on duplicate port removal in del_fdb_flow() (LP:

[Yahoo-eng-team] [Bug 1460164] Re: restart of openvswitch-switch causes instance network down when l2population enabled

** Also affects: cloud-archive/icehouse Importance: Undecided Status: New ** Changed in: cloud-archive/icehouse Status: New => Fix Committed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron.

[Yahoo-eng-team] [Bug 1460164] Re: restart of openvswitch-switch causes instance network down when l2population enabled

** Also affects: neutron (Ubuntu Xenial) Importance: High Status: Triaged ** Also affects: neutron (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: neutron (Ubuntu Xenial)

[Yahoo-eng-team] [Bug 1460164] Re: restart of openvswitch-switch causes instance network down when l2population enabled

** Description changed: + [Impact] + Restarts of openvswitch (typically on upgrade) result in loss of tunnel connectivity when the l2population driver is in use. This results in loss of access to all instances on the effected compute hosts + + [Test Case] + Deploy cloud with

[Yahoo-eng-team] [Bug 1460164] Re: restart of openvswitch-switch causes instance network down when l2population enabled

Reviewed: https://review.openstack.org/259485 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=17c14977ce0e2291e911739f8c85838f1c1f3473 Submitter: Jenkins Branch:master commit 17c14977ce0e2291e911739f8c85838f1c1f3473 Author: James Page Date:

[Yahoo-eng-team] [Bug 1460164] Re: restart of openvswitch-switch causes instance network down when l2population enabled

The fdb_add method checks to see if the agent already has a registered ofport for each tunnel it requires - this is now stale, so results in the tunnel setup being skipped - the tunnel ports are still present in the ovsdb - however all of the flows are missing resulting in full loss of instance