On 8 March 2017 at 09:42, Russell Bryant <[email protected]> wrote: > On Wed, Mar 8, 2017 at 2:18 AM, Gurucharan Shetty <[email protected]> wrote: > > There are multiple reasons why a interface can exist > > in the Open vSwitch database but not exist in the system. > > For e.g, a restart of a host after a system crash. Ideally, > > whoever added the interface in the Open vSwitch database > > should remove those interfaces. But that usually does not > > happen in practise. Based on experience, I have observerd > > practice and observed > Ugh. Though I fixed this locally, I forgot to regenerate the patch to apply. So the commit message still has the typo. Sorry about that.
> > > that on any long lasting OVS installation there are always > > a couple of stale interfaces. > > > > When a stale interface remains in the Open vSwitch database > > and the container/VM initially backing that stale interface > > is moved to a different machine, the two ovn-controllers > > start over-writing the OVN-SB's port_binding table in a loop. > > > > This situation can be avoided, if ovn-controller only binds > > the interfaces that actually have a valid 'ofport'. > > > > Signed-off-by: Gurucharan Shetty <[email protected]> > > This sounds reasonable to me. > > Acked-by: Russell Bryant <[email protected]> > _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
