yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #57116
[Bug 1623708] Re: OVS trunk management does not tolerate agent failures
Reviewed: https://review.openstack.org/375132
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4148102f736f7191dd5bf1c2c41505c338c6dc56
Submitter: Jenkins
Branch: master
commit 4148102f736f7191dd5bf1c2c41505c338c6dc56
Author: Armando Migliaccio <armamig@xxxxxxxxx>
Date: Thu Sep 22 13:15:11 2016 -0700
Process OVS trunk bridges associated to VM deletes
If a VM is deleted while the OVS agent is down, upon
restart the OVS trunk bridge is deleted successfully
but the patch ports integration bridge side are left
behind.
This patch makes sure the bridge as well as its peers
are cleaned up.
Closes-bug: #1623708
Change-Id: I3f010755fdb6501753d20357ad2cd0d6c02cf22a
** Changed in: neutron
Status: In Progress => 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/1623708
Title:
OVS trunk management does not tolerate agent failures
Status in neutron:
Fix Released
Bug description:
It is clear that patch [1] will be unable to complete in time for RC1.
This bug report is tracking the effort to complete it post RC1.
We need to revise the OVSDBHandler module to make sure we can tolerate
loss of events (OVSDB and Remote) in case of agent failures.
[1] https://review.openstack.org/#/c/365176/
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1623708/+subscriptions
References